Actually, I have commented that line out initially when I first looked at
the sshd_config file. Either way, I compiled it and installed from
scratch. I also recompiled the kernel (2.4) so everything is great now
(other that I forgot to compile with vfat support!).
Thanks
Mohammed Elzubeir
Gene
You might try Saito's workaround, it worked for me.
On Sat, 27 Jan 2001, Mohammed Elzubeir wrote:
>
>Nathan,
>
>That was not my intention, to 'flame' but possibly 'bitch'. I am new to
>Debian and how they do things, and so far it has been the hardest Linux
>distribution to
>understand. If for an
Nathan,
That was not my intention, to 'flame' but possibly 'bitch'. I am new to
Debian and how they do things, and so far it has been the hardest Linux
distribution to
understand. If for anything, I appreciate the people on this mailing list
as they have been beyond helpful. You may consider it a
On Sat, Jan 27, 2001 at 07:46:26PM -0600, Mohammed Elzubeir wrote:
> Getting on dselect and removing all that ssh related stuff. Downloaded
> OpenSSL and compiled it and installed. Did the same for OpenSSH and now
> everything is great. I am never depending on Debian packaging. Period.
The please,
I hardly knows english, I don't know whether it will be able to answer
securely from now on
At Fri, 26 Jan 2001 19:38:04 -0600 (CST),
Mohammed Elzubeir wrote:
> ssh_exchange_identification: Connection closed by remote host
/etc/ssh/sshd_config
I resolved this problem by doing the following:
Getting on dselect and removing all that ssh related stuff. Downloaded
OpenSSL and compiled it and installed. Did the same for OpenSSH and now
everything is great. I am never depending on Debian packaging. Period.
Thanks everyone for your help, I d
Actually, I have commented that line out initially when I first looked at
the sshd_config file. Either way, I compiled it and installed from
scratch. I also recompiled the kernel (2.4) so everything is great now
(other that I forgot to compile with vfat support!).
Thanks
Mohammed Elzubeir
Gen
You might try Saito's workaround, it worked for me.
On Sat, 27 Jan 2001, Mohammed Elzubeir wrote:
>
>Nathan,
>
>That was not my intention, to 'flame' but possibly 'bitch'. I am new to
>Debian and how they do things, and so far it has been the hardest Linux
>distribution to
>understand. If for a
Nathan,
That was not my intention, to 'flame' but possibly 'bitch'. I am new to
Debian and how they do things, and so far it has been the hardest Linux
distribution to
understand. If for anything, I appreciate the people on this mailing list
as they have been beyond helpful. You may consider it
On Sat, Jan 27, 2001 at 07:46:26PM -0600, Mohammed Elzubeir wrote:
> Getting on dselect and removing all that ssh related stuff. Downloaded
> OpenSSL and compiled it and installed. Did the same for OpenSSH and now
> everything is great. I am never depending on Debian packaging. Period.
The please
I hardly knows english, I don't know whether it will be able to answer
securely from now on
At Fri, 26 Jan 2001 19:38:04 -0600 (CST),
Mohammed Elzubeir wrote:
> ssh_exchange_identification: Connection closed by remote host
/etc/ssh/sshd_config
---
On Sat, Jan 27, 2001 at 03:39:02PM +0100, Sune Kirkeby wrote:
>
> I don't know how or why, but it does _not_ clear the scroll-back buffer
> on my console, "chvt 63 ; reset -Q ; chvt 1" does though.
you don't need the reset -Q there. the simple act of changing VCs
clears the scrollback history.
I resolved this problem by doing the following:
Getting on dselect and removing all that ssh related stuff. Downloaded
OpenSSL and compiled it and installed. Did the same for OpenSSH and now
everything is great. I am never depending on Debian packaging. Period.
Thanks everyone for your help, I
On Sat, Jan 27, 2001 at 08:53:53AM -0600, wes schreiner wrote:
> A winner! OK, it flashes if vt 63 is in use, but otherwise it's great.
yeah but who actually uses that many terminals ;-)
--
Ethan Benson
http://www.alaska.net/~erbenson/
pgpjeqEfQCavQ.pgp
Description: PGP signature
Guys! it's a real problem: according to Christian Kurz's bitching at me,
there have already been four bugs filed about this issue. Trivial
workarounds like /etc/hosts entries or sshing as root aren't going to
help. sshd is broken in sid ATM, and unless you actually have a good
workaround, I'd su
On Sat, Jan 27, 2001 at 01:53:31AM +0100, Tim van Erven wrote:
> [... how to clear screen...]
> It's still got a hackish feel about it however. Anyone know if there's
> a cleaner way to do this?
you could use seq 1000 to count from 1 to 1000, instead of printing
newlines.
--
#define X(x,y) x##
On Sat, Jan 27, 2001 at 03:39:02PM +0100, Sune Kirkeby wrote:
>
> I don't know how or why, but it does _not_ clear the scroll-back buffer
> on my console, "chvt 63 ; reset -Q ; chvt 1" does though.
you don't need the reset -Q there. the simple act of changing VCs
clears the scrollback history.
Hello,
On Sat, Jan 27, 2001 at 10:24:01AM -0600, Mohammed Elzubeir wrote:
>
> I just changed it and removed the last ':', and now I get "Permission
> denied".
Failing all else, SSH should ask you for a password if you have the
server configured to allow this.
In the SSH source code, in sshconne
Okay, this is the final thing, I don't understand these files too well,
but here is my /etc/pam.d/ssh file:
authrequiredpam_nologin.so
authrequiredpam_unix.so
authrequiredpam_env.so # [1]
account requiredpam_unix.so
session requiredpa
On Sat, Jan 27, 2001 at 08:53:53AM -0600, wes schreiner wrote:
> A winner! OK, it flashes if vt 63 is in use, but otherwise it's great.
yeah but who actually uses that many terminals ;-)
--
Ethan Benson
http://www.alaska.net/~erbenson/
PGP signature
[ Mohammed Elzubeir ]
> I just changed it and removed the last ':', and now I get "Permission
> denied". This is crazy. I just want to be able to ssh.. that's all.
> Why is it so damn weird on Debian..
I'm going to risk my neck and make an obvious suggestion, look for pam-
and ssh-related messages
Guys! it's a real problem: according to Christian Kurz's bitching at me,
there have already been four bugs filed about this issue. Trivial
workarounds like /etc/hosts entries or sshing as root aren't going to
help. sshd is broken in sid ATM, and unless you actually have a good
workaround, I'd s
On Sat, Jan 27, 2001 at 01:53:31AM +0100, Tim van Erven wrote:
> [... how to clear screen...]
> It's still got a hackish feel about it however. Anyone know if there's
> a cleaner way to do this?
you could use seq 1000 to count from 1 to 1000, instead of printing
newlines.
--
#define X(x,y) x#
Hello,
On Sat, Jan 27, 2001 at 10:24:01AM -0600, Mohammed Elzubeir wrote:
>
> I just changed it and removed the last ':', and now I get "Permission
> denied".
Failing all else, SSH should ask you for a password if you have the
server configured to allow this.
In the SSH source code, in sshconn
Okay, this is the final thing, I don't understand these files too well,
but here is my /etc/pam.d/ssh file:
authrequiredpam_nologin.so
authrequiredpam_unix.so
authrequiredpam_env.so # [1]
account requiredpam_unix.so
session requiredp
[ Mohammed Elzubeir ]
> I just changed it and removed the last ':', and now I get "Permission
> denied". This is crazy. I just want to be able to ssh.. that's all.
> Why is it so damn weird on Debian..
I'm going to risk my neck and make an obvious suggestion, look for pam-
and ssh-related message
No of course not. I checked my sshd_config file, and I definitely would
not allow root to ssh directly.
Mohammed Elzubeir
General Access Labs (x2825)
http://www.cas.unt.edu/gal/
College of Arts & Sciences
University of North Texas
[EMAIL PROTECTED]
On Sat, 27 Jan 2001, Laurent Luyckx wrote:
>
Mohammed Elzubeir wrote:
> I just changed it and removed the last ':', and now I get "Permission
> denied". This is crazy. I just want to be able to ssh.. that's all. Why is
> it so damn weird on Debian.. this is the first time EVER that I had a hard
> time setting up ssh, or ANY unix or linux.
>
Hi, I've just installed my new iptables rules in my debian box, and I've got
plenty of connections from different hosts to port 10...What can it be? I'v
searched about port 10 connections, but the only thing I know is that it's
unassigned...Any ideas?
Regards
--
http://www.somoslopeor.com
I just changed it and removed the last ':', and now I get "Permission
denied". This is crazy. I just want to be able to ssh.. that's all. Why is
it so damn weird on Debian.. this is the first time EVER that I had a hard
time setting up ssh, or ANY unix or linux.
later
Mohammed Elzubeir
General
No of course not. I checked my sshd_config file, and I definitely would
not allow root to ssh directly.
Mohammed Elzubeir
General Access Labs (x2825)
http://www.cas.unt.edu/gal/
College of Arts & Sciences
University of North Texas
[[EMAIL PROTECTED]]
On Sat, 27 Jan 2001, Laurent Luyckx wrote:
Ethan Benson wrote:
>
> On Sat, Jan 27, 2001 at 07:37:59AM -0600, wes schreiner wrote:
> > I'd still like to
> > see a cleaner way to clear the CONSOLE scroll-back. All of the
> > suggestions so far (clear, reset -Q, ESC[2J ESC[0;0H in /etc/issue) just
> > clear the immediately visible screen, n
Mohammed Elzubeir wrote:
> Okay, I don't know how this has to do with my dns config (which were
> screwy anyway).. so I went ahead and setup my dns server like it should be
> (as a slave nameserver) and it works fine. I am able to connect to the
> 'outside' from it, but not to it.
>
> I also had
[ wes schreiner ]
> Not that I can see, though I'd love to know of a clean way to clear
> the scroll-back buffer. I agree it's a bit hackish. Can anyone come
> up with something better?
[ Cesar Crusius wrote ]
> reset -Q
[ Tal Danzig ]
> Works, in an xterm as well. That's neat, I'll change all
Mohammed Elzubeir wrote:
> I just changed it and removed the last ':', and now I get "Permission
> denied". This is crazy. I just want to be able to ssh.. that's all. Why is
> it so damn weird on Debian.. this is the first time EVER that I had a hard
> time setting up ssh, or ANY unix or linux.
>
Hi, I've just installed my new iptables rules in my debian box, and I've got plenty of
connections from different hosts to port 10...What can it be? I'v searched about port
10 connections, but the only thing I know is that it's unassigned...Any ideas?
Regards
--
http://www.somoslopeor.com
On Sat, Jan 27, 2001 at 07:37:59AM -0600, wes schreiner wrote:
>
> # ~/.bash_logout: executed by bash(1) when login shell exits.
> # when leaving the console clear the screen to increase privacy
> case "`tty`" in
> /dev/tty[0-9]) echo ^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L\
> ^L^L^
I just changed it and removed the last ':', and now I get "Permission
denied". This is crazy. I just want to be able to ssh.. that's all. Why is
it so damn weird on Debian.. this is the first time EVER that I had a hard
time setting up ssh, or ANY unix or linux.
later
Mohammed Elzubeir
General
Alexis Paul Musgrave wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> In my .bash_logout I have:
>
> case "`tty`" in
> /dev/tty[0-9]) clear
> esac
>
> This works perfectly on tty's, and I don't think you need this on
> pty's.
No, this doesn't work, at least not on vgacon or m
Ethan Benson wrote:
>
> On Sat, Jan 27, 2001 at 07:37:59AM -0600, wes schreiner wrote:
> > I'd still like to
> > see a cleaner way to clear the CONSOLE scroll-back. All of the
> > suggestions so far (clear, reset -Q, ESC[2J ESC[0;0H in /etc/issue) just
> > clear the immediately visible screen,
Mohammed Elzubeir wrote:
> Okay, I don't know how this has to do with my dns config (which were
> screwy anyway).. so I went ahead and setup my dns server like it should be
> (as a slave nameserver) and it works fine. I am able to connect to the
> 'outside' from it, but not to it.
>
> I also ha
[ wes schreiner ]
> Not that I can see, though I'd love to know of a clean way to clear
> the scroll-back buffer. I agree it's a bit hackish. Can anyone come
> up with something better?
[ Cesar Crusius wrote ]
> reset -Q
[ Tal Danzig ]
> Works, in an xterm as well. That's neat, I'll change al
On Sat, Jan 27, 2001 at 07:37:59AM -0600, wes schreiner wrote:
>
> # ~/.bash_logout: executed by bash(1) when login shell exits.
> # when leaving the console clear the screen to increase privacy
> case "`tty`" in
> /dev/tty[0-9]) echo ^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L^L\
> ^L^L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In my .bash_logout I have:
case "`tty`" in
/dev/tty[0-9]) clear
esac
This works perfectly on tty's, and I don't think you need this on
pty's.
,_Muz_
- --
|- Alexis Paul (Muz) Musgrave - <[EMAIL PROTECTED],com> <[EMAIL PROTECTED]>
-|
|- Ru
Alexis Paul Musgrave wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> In my .bash_logout I have:
>
> case "`tty`" in
> /dev/tty[0-9]) clear
> esac
>
> This works perfectly on tty's, and I don't think you need this on
> pty's.
No, this doesn't work, at least not on vgacon or
The recent mgetty upload security fix, and an NMU upload (of mgetty) to
unstable yesterday reminded me of a serious issue we still have to address.
Sometimes, security patches made by the security team (and made available
through security.debian.org) are reverted on mistake by maintainers on the
n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In my .bash_logout I have:
case "`tty`" in
/dev/tty[0-9]) clear
esac
This works perfectly on tty's, and I don't think you need this on
pty's.
,_Muz_
- --
|- Alexis Paul (Muz) Musgrave - <[EMAIL PROTECTED]> -|
|- Running Debian GNU/Linux
The recent mgetty upload security fix, and an NMU upload (of mgetty) to
unstable yesterday reminded me of a serious issue we still have to address.
Sometimes, security patches made by the security team (and made available
through security.debian.org) are reverted on mistake by maintainers on the
48 matches
Mail list logo
