On Thursday 31 May 2007 13:14, Mauro Faccenda wrote: > On Thursday 31 May 2007 07:42, Mick wrote: > > On Wednesday 30 May 2007 21:42, Mauro Faccenda wrote: [snip] > > debug1: Offering public key: /home/michael/.ssh/id_dsa > > debug1: Authentications that can continue: > > publickey,gssapi-with-mic,password debug1: Next authentication method: > > password > > ====================================== > > that's strange. > > which version of openssh do you use in the server and the client? > mine: > client: OpenSSH_4.5p1 > server: OpenSSH_4.4p1
Installed versions: 4.5_p1-r1(19:45:58 02/23/07) (X -X509 -chroot -hpn -kerberos ldap -libedit pam -selinux -skey -smartcard -static tcpd) > > That's right, so why does it: > > ====================================== > > debug1: Trying private key: /home/michael/.ssh/id_rsa <--this doesn't > > exist debug1: Offering public key: /home/michael/.ssh/id_dsa <--this is > > my private key > > ====================================== > > i didn't noticed this line... really strange. > > how your id_dsa was created? is it corrupted or does it has a public key on > it instead? It was created with 'ssh-keygen -t dsa'. > you should try creating your key pair again with: > > $ ssh-keygen -t dsa I would, but it seems to work fine with other servers, hence the point of this thread. What I am going to try out nevertheless is generating an RSA key and see if the server accepts it. Perhaps as Hans-Werner suggested the server may have been configured to only use dsa keys (I find this odd, but I don't know much about RH). > i would like to see the content of this file (or, at least the "headers"), > but its a PRIVATE key. ;) > > the "headers" of mine: > > -----BEGIN DSA PRIVATE KEY----- > Proc-Type: 4,ENCRYPTED > DEK-Info: DES-EDE3-CBC,933FEB2C1C691496 This is mine: -----BEGIN DSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC, XXXXXXXXXXX[snip] -- Regards, Mick
pgpicfna9L7St.pgp
Description: PGP signature
