ssh-ing to an old suse.

Mon, Nov 19, 2007 at 09:16:21PM +0100, Carlos E. R. wrote:

The Monday 2007-11-19 at 14:54 +0100, Lukas wrote:
or even
>
ssh -vv telperion.valinor
>
Debug output should tell you more.

ssh has three debug levels. You can also try ssh -vvv



And there it stops. Lets try double -vv.



cer@nimrodel:~ssh -vv telperion.valinor
SSH_4.6p1, SSL 0.9.8e 23 Feb 2007
debug1: Reading configuration data /home/cer/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to telperion.valinor [192.168.1.11] port 22.
debug1: Connection established.
debug2: key_type_from_name: unknown key type ''
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug2: key_type_from_name: unknown key type ''
debug1: identity file /home/cer/.ssh/id_rsa type 1
debug2: key_type_from_name: unknown key type ''
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug2: key_type_from_name: unknown key type ''
debug1: identity file /home/cer/.ssh/id_dsa type 2

You have no type2 rsa key, only type2 dss and type1 rsa keys.
It seems that both keys have been create with another software.
Because most installations default to type2 rsa, you may try to
generate a key on 10.3 with ssh-keygen -t rsa -f <keyfile>

Use this new key as ~/.ssh/id_rsa on the 10.3 side and add the
public key to ~/.ssh/authorized_kes on the 7.3 side (the private
type1 key is usally expected in ~/.ssh/identity).


debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received

At least the host keys seems to be okay.
To find out more about the user authentication, you should increase
the loglevel and compare the ssh_config on the client side with the
sshd_config on the server side (esp. parameters like
, UsePrivilegeSeparation, UsePAM that
had issues in older ssh versions).


I have also enabled debug mode in the server side (7.3). I'll have to do tricks to paste the server log here

[] (scp-ing /var/log/messages from 7.3 to 10.3)

Importing server side log:

Nov 19 21:08:39 telperion sshd[2387]: Connection closed by ::ffff:192.168.1.12
Nov 19 21:09:39 telperion sshd[2388]: Connection closed by ::ffff:192.168.1.12
Nov 19 21:12:05 telperion sshd[974]: Received signal 15; terminating.
Nov 19 21:12:06 telperion sshd[2414]: debug1: Bind to port 22 on ::.
Nov 19 21:12:06 telperion sshd[2414]: Server listening on :: port 22.
Nov 19 21:12:06 telperion sshd[2414]: debug1: Bind to port 22 on 0.0.0.0.
Nov 19 21:12:06 telperion sshd[2414]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.

Are you sure that sshd is listening on th correct IP (v4 or v6) and port?




PGP SIGNATURE
Version: GnuPG v1.4.6 (GNU/Linux)




Mq9dqSWWnaY=
=Cr5D
PGP SIGNATURE