On 31/05/07, Mick <[EMAIL PROTECTED]> wrote:
On Thursday 31 May 2007 13:14, Mauro Faccenda wrote:
> 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).
Not sure if this server has been configured to only use its own generated keys (is this possible?) because it will not accept a new RSA key of mine: ========================================== debug1: Found key in /home/michael/.ssh/known_hosts:18 debug1: ssh_rsa_verify: signature correct debug1: Enabling compression at level 6. debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: publickey debug1: Offering public key: .ssh/id_rsa debug1: Authentications that can continue: publickey,gssapi-with-mic,password debug1: Next authentication method: password ========================================== It think it's high time I have words with the sysadmin - wish me luck. ;-) -- Regards, Mick
smime.p7s
Description: S/MIME Cryptographic Signature
