What happens if you ssh -v -v -v to both the good machine and the bad machine? The output below suggests that the bad machine is choking on both your rsa key and your dsa key. The good machine only chokes on the dsa key, so maybe it's using whatever rsa key you give it (and perhaps this is a different rsa key than you supplied to the bad machine). The verbose output from the ssh client would confirm this. For example, I think the ssh2 protocol uses only dsa keys. -chris
"Luigi Fabio" <[EMAIL PROTECTED]> writes: > Well, I finally got something different. > I upgraded to 2.5.2p2 and rebuilt everything. Very good, ./sshd -ddd - > p 9xxx gets me this on the working machine: > > debug1: Seeding random number generator > debug1: sshd version OpenSSH_2.5.2p2 > debug1: load_private_key_autodetect: type 0 RSA1 > debug3: Bad RSA1 key file /etc/sshd/ssh_host_dsa_key. > debug1: read SSH2 private key done: name dsa w/o comment success 1 > debug1: load_private_key_autodetect: type 2 DSA > socket: Address family not supported by protocol > debug1: Bind to port 9399 on 0.0.0.0. > Server listening on 0.0.0.0 port 9399. > Generating 768 bit RSA key. > RSA key generation complete. > > while it gets me this on the non-working machine: > > debug1: Seeding random number generator > debug1: sshd version OpenSSH_2.5.2p2 > debug1: load_private_key_autodetect: type 0 RSA1 > debug3: Bad RSA1 key file /etc/sshd/ssh_host_rsa_key. > debug1: read SSH2 private key done: name rsa w/o comment success 1 > debug1: load_private_key_autodetect: type 1 RSA > debug3: Bad RSA1 key file /etc/sshd/ssh_host_dsa_key. > debug1: read SSH2 private key done: name dsa w/o comment success 1 > debug1: load_private_key_autodetect: type 2 DSA > socket: Address family not supported by protocol > debug1: Bind to port 9020 on 0.0.0.0. > Server listening on 0.0.0.0 port 9020. > Generating 768 bit RSA key. > RSA key generation complete. > > Any ideas would still be very welcome. > > > Regards, > Luigi Fabio - [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
