Comments on: Debian / Ubuntu Linux Public key Blacklisted (see ssh-vulnkey(1)) Error and Solution http://www.cyberciti.biz/faq/linux-publickey-blacklisted-see-ssh-vulnkey1-error/ Every answer asks a more beautiful question. Fri, 10 Feb 2012 19:55:56 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: greylionhttp://www.cyberciti.biz/faq/linux-publickey-blacklisted-see-ssh-vulnkey1-error/#comment-43480 greylion Sat, 29 Aug 2009 17:56:42 +0000 http://www.cyberciti.biz/faq/?p=1159#comment-43480 When scp'ing the new id_*pub files over, it asks for the passwd. After typing in the passwd, I get these errors: setterm: $TERM is not defined. setterm: $TERM is not defined. scp: .ssh/authorized_keys2: No such file or directory (Debian 5.0/lenny 32-bit) Apparently, I don't need to do that, it works anyway. Maybe the pubkeys get transferred upon first login, when you're asked yes/no to continue connecting? I did need to delete a couple of old ones in known_hosts, though, for both root and my (only) user. When scp’ing the new id_*pub files over, it asks for the passwd.
After typing in the passwd, I get these errors:
setterm: $TERM is not defined.
setterm: $TERM is not defined.
scp: .ssh/authorized_keys2: No such file or directory
(Debian 5.0/lenny 32-bit)

Apparently, I don’t need to do that, it works anyway.
Maybe the pubkeys get transferred upon first login, when you’re asked yes/no to continue connecting?
I did need to delete a couple of old ones in known_hosts, though, for both root and my (only) user.

]]> By: Gavin McQuillanhttp://www.cyberciti.biz/faq/linux-publickey-blacklisted-see-ssh-vulnkey1-error/#comment-41454 Gavin McQuillan Mon, 04 May 2009 03:32:46 +0000 http://www.cyberciti.biz/faq/?p=1159#comment-41454 Hi. This was a quick, helpful guide to negotiating this situation. However, I found that one extra step was helpful in making the remote system accessible again (if you run into "Permission denied (publickey)" error) : from the desktop system: $ ssh-add [enter password] Now you shouldn't have any trouble accessing the remove server. Hi.

This was a quick, helpful guide to negotiating this situation. However, I found that one extra step was helpful in making the remote system accessible again (if you run into “Permission denied (publickey)” error) :

from the desktop system:
$ ssh-add
[enter password]

Now you shouldn’t have any trouble accessing the remove server.

]]>