Tried to login to a newly baked Raspberry Pi with Raspbian Wheezy 2014 image on the SD card, but it wouldn’t let me type in the password!
I fired off ssh pi@192.168.1.185 -vvv
to see what actually happened. To my surprise, I could see that the password
option was offered back to my SSH client, but it didn’t bite. Instead it simply ended with: too many authentication failures
. Looking again at the verbose output, I could see that I had no less than 5 SSH keys that where being offered to the remote system (rpi).
From that, I got that it probably didn’t like being offered that many failed login attempts, so once I turned off offering SSH keys, I finally got the prompt I wanted!
I turned off offering SSH keys by using the -i
flag: ssh pi@192.168.1.185 -i /dev/null
. There’s probably a better way, but this was good enough for me to bootstrap it with Puppet (which puts my keys where I want them).
Example output:
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/username/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.1.185 [192.168.1.185] port 22.
debug1: Connection established.
debug1: identity file /home/username/.ssh/id_rsa type -1
debug1: identity file /home/username/.ssh/id_rsa-cert type -1
debug1: identity file /home/username/.ssh/id_dsa type 2
debug1: identity file /home/username/.ssh/id_dsa-cert type -1
debug1: identity file /home/username/.ssh/id_ecdsa type -1
debug1: identity file /home/username/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/username/.ssh/id_ed25519 type -1
debug1: identity file /home/username/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debian-4+deb7u2
debug1: match: OpenSSH_6.0p1 Debian-4+deb7u2 pat OpenSSH* compat 0x04000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA 4c:5b:a9:c5:a7:be:e9:29:38:7c:fe:af:ee:f3:15:d9
debug1: Host '192.168.1.185' is known and matches the ECDSA host key.
debug1: Found key in /home/username/.ssh/known_hosts:182
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering DSA public key: /home/username/.ssh/id_dsa
debug1: Authentications that can continue: publickey,password
debug1: Offering DSA public key: username@wendt-z61t
debug1: Authentications that can continue: publickey,password
debug1: Offering DSA public key: username@wendt-z61t
debug1: Authentications that can continue: publickey,password
debug1: Offering DSA public key: username@t61-laptopt
debug1: Authentications that can continue: publickey,password
debug1: Offering RSA public key: bkp@hemma
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/username/.ssh/id_rsa
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
Received disconnect from 192.168.1.185: 2: Too many authentication failures for pi
username@fredrik-t410:~$