Arch Linux

beachcoder

Member

Registered: 2009-10-08

Posts: 130

OpenSSH and putty: "Server refused our key" after full system upgrade

Hello!

To get git to run, I made  a full system upgrade on my virtual server's Arch Linux distro. After a reboot, I can't connect via Putty anymore, which worked before about more than 56 days without any problems. The only message I get is: "Server refused our key".

It worked without any problems before. I don't have any other access to my machine than the RSA keys. Very nice... I need this machine for work. I did change nothing at all on the openssh-configuration.

Any ideas?

beachcoder -.-

Last edited by beachcoder (2010-04-23 10:19:31)

beachcoder

Member

Registered: 2009-10-08

Posts: 130

Re: OpenSSH and putty: "Server refused our key" after full system upgrade

To connect from another Linux-machine is even not possible:

debug1: try privkey: id_user
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
Enter passphrase for key 'id_user': 
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey
debug2: we sent a publickey packet, wait for reply
debug1: authentications that can continue: publickey
debug2: we did not send a packet, disable method
debug1: no more auth methods to try
Permission denied (publickey).
debug1: Calling cleanup 0x80640b0(0x0)

beachcoder...

anrxc

Member

From: Croatia

Registered: 2008-03-22

Posts: 834

Website

Re: OpenSSH and putty: "Server refused our key" after full system upgrade

Probably this: http://bugs.archlinux.org/task/18781

Last edited by anrxc (2010-04-23 12:42:20)

---

You need to install an RTFM interface.

beachcoder

Member

Registered: 2009-10-08

Posts: 130

Re: OpenSSH and putty: "Server refused our key" after full system upgrade

Probably this: http://bugs.archlinux.org/task/18781

This could be the problem (and solution). But as mentioned, I don't have a direct access to that machine, because it's a virtual server running on a friend's server who I can't contact right now.
So there is not way to get in, huh? Any other SSH login methods are disabled on that machine.

What a bummer! But anyway, thanks for this info.

beachcoder