I used puttygen to tát generate both my public and private key files (ssh2, 2048 bit). I have phối up the settings in putty correctly and it is using the correct private key tệp tin. As for the public key, (I am using these keys for root) it is in /root/.ssh/authorized_keys

I have tried using chmod on .ssh to tát 700 and on authorized_keys to tát 400. That did not tự anything.

Does anyone have any recommendations?

edit: here's an ls -ldZ of my .ssh thư mục and authorized_keys file

drwx------ root root ?                                /root/.ssh
-rw------- root root ?                                /root/.ssh/authorized_keys

Rui F Ribeiro

57.5k26 gold badges152 silver badges233 bronze badges

asked May 13, năm 2016 at 3:06

8

I also had this problem seemingly out of nowhere, but only with FileZilla and not Putty. (key based auth)

For bu the solution was simple (when I read the tip here) to tát just update Putty including Pageant.

AdminBee

23.3k25 gold badges52 silver badges76 bronze badges

answered Jan 23, 2022 at 14:29

2

Set LogLevel to tát DEBUG in sshd_config, and I think you'll find (in auth.log of course) a reason why you publick key is refused.

Archemar

31.9k18 gold badges72 silver badges106 bronze badges

answered May 13, năm 2016 at 8:03

2

Looking at the log /var/log/secure showed that it was just downright refused. I'm somewhat new to tát centos since I'm mainly a debian kind of guy, ví I was unaware of /var/log/secure

After checking this and doing a bit of searching, it turns out PermitRootLogin no needs to tát be PermitRootLogin without-password if you want to tát specifically use just keys for root login. That did the trick. Thanks everyone for contributing.

answered May 13, năm 2016 at 22:23

We had the same error ("Server refused public-key signature despite accepting key") while trying to tát connect to tát ssh to tát a server using a key as root. It turned out that the problem was caused by the fact that the server's SSH configuration wasn't allowing the user root to tát use SSH keys.

answered Jun 4, 2019 at 8:46

Some protocol deprecation in progress..

  1. Upgrade putty to tát version 0.77 (that includes puttygen)
  2. Run puttygen, load id_rsa tệp tin, generate new PPK (overwrite old one)

answered Jul 5, 2022 at 8:59

1

I had this problem seemingly out of nowhere. Previously I'd added ssh keys and connected without issue. Even the SSH button to tát connect to tát the VM available through the Google Cloud Console trang web would fail to tát register keys.

The problem was that Google's Linux Guest Environment wasn't running. I resolved my issue by following the directions for In-Place Install: Linux Guest Environment.

answered Dec 4, 2018 at 20:10

We upgraded Ubuntu from 18 to tát trăng tròn and experienced that error message. For hours I tried to tát get RSA up and running again, but with no success.

In the kết thúc, the solution was to tát create an ECDSA key in putty and no changes to tát any ssh configs were necessary.

AdminBee

23.3k25 gold badges52 silver badges76 bronze badges

answered Aug 7, 2023 at 7:22

You must log in to tát answer this question.

Not the answer you're looking for? Browse other questions tagged

.