permission denied (publickey) bug

[Toukmond]

I cannot ssh into my raspberry pi with Secure Shell as I get a permission denied (publickey) error. If I ssh into my raspberry pi with the same key using crosh on the same computer it works fine. This isn't a huge issue as I can just use crosh but I thought I should report it.

[Robert Ginda]

Can you try with the "SSH Arguments" field set to "-v" and report back?  The most likely cause is that something went wrong importing the key.

On Mon, Dec 30, 2013 at 6:49 PM, Toukmond <jacob...@gmail.com> wrote:

I cannot ssh into my raspberry pi with Secure Shell as I get a permission denied (publickey) error. If I ssh into my raspberry pi with the same key using crosh on the same computer it works fine. This isn't a huge issue as I can just use crosh but I thought I should report it.

--
You received this message because you are subscribed to the Google Groups "chromium-hterm" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-hterm/bc2877d0-a1f4-482c-ae6e-94ef6fc019ad%40chromium.org.

[Jacob Adams]

This is the entire log as reported by secure shell, with my ip taken out for obvious reasons:

OpenSSH_5.9p1, OpenSSL 1.0.0e 6 Sep 2011
debug1: Connecting to xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] port 22.
debug1: Connection established.
debug1: identity file /.ssh/id_rsa type -1
debug1: identity file /.ssh/id_rsa-cert type -1
debug1: identity file /.ssh/id_dsa type -1
debug1: identity file /.ssh/id_dsa-cert type -1
debug1: identity file /.ssh/id_ecdsa type -1
debug1: identity file /.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debian-4
debug1: match: OpenSSH_6.0p1 Debian-4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 zl...@openssh.com
debug1: kex: client->server aes128-ctr hmac-md5 zl...@openssh.com
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA d9:b9:59:a5:d7:53:16:0c:bf:63:64:d9:b8:d4:eb:fd
debug1: Host 'xxx.xxx.xxx.xxx' is known and matches the ECDSA host key.
debug1: Found key in /.ssh/known_hosts:4
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
Raspbian GNU/Linux 7
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /.ssh/id_rsa
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: Trying private key: /.ssh/id_dsa
debug1: could not open key file '/.ssh/id_dsa': Broken pipe
debug1: Trying private key: /.ssh/id_ecdsa
debug1: could not open key file '/.ssh/id_ecdsa': Broken pipe
debug1: No more authentication methods to try.
Permission denied (publickey).
NaCl plugin exited with status code 255.

The private key file was named raspbian. It does not appear to even try to check this key even though I know I imported it.

[Robert Ginda]

Did you select key from the Identity dropdown in the connection dialog?  If it doesn't show up there, it's not imported correctly. Secure Shell is picky when it comes to importing keys.  See https://github.com/libapps/libapps-mirror/blob/master/nassh/doc/faq.txt#L139

[Jacob Adams]

It doesn't show up but I don't have my public key so that's probably the problem 

Jacob