Carl Cerecke wrote:
On 13/08/05, Steve Holdoway <[EMAIL PROTECTED]> wrote:
Could it be corrupt ssh or ssl daemons? As it's one of those things that
often lags behind the current versions, so building from source won't
hurt. FC4 uses current openssh, but 0.9.7f openssl, and debian sarge is
at OpenSSH_3.8.1p1 Debian-8.sarge.4 and OpenSSL 0.9.7e.
ftp://ftp.planetmirror.com/pub/OpenBSD/OpenSSH/portable/openssh-4.1p1.tar.gz
and http://www.openssl.org/source/openssl-0.9.8.tar.gz are the latest
versions.
Thanks, but why would they be corrupt? They are just the stock
standard suse 9.1 versions. ssh works OK. sshd does not. I can try
re-installing, I suppose.
Cheers,
Carl.
There're plenty of reasons why they could get corrupt - was just a
thought. If you've updated any software on your pc, then it could be
affecting sshd.
Does file sshd ( usually in /usr/sbin?? ) give a logical response?
Is there already something else running on port 22? nmap or telnet
localhost 22 should answer that one.
Has /etc/ssh/sshd_config ( that's where it is on debian/FC4 ) changed
lately?
$0.02
Steve
