Anyone with experience using ssh on Raspberry Pi Model B

I am having very irritating problems using ssh from Fedora 15 box to a Raspberry Pi Model B board, running OpenELEC 2.99.5. It appears that the ssh client can connect with the ssh server on the Raspberry Pi, but authentication fails. If anyone has used this board, and has experience successfully using ssh to the board, I would like to contact you.

Reply to
dakupoto
Loading thread data ...

I have never had any problems with that.

Have you got "ssh -v" output to support your hypothesis.

--
?? 100% natural 

--- news://freenews.netfront.net/ - complaints: news@netfront.net ---
Reply to
Jasen Betts

SSH from PuTTY on Windows 7 to Raspbian on Raspberry Pi works for me.

Reply to
Andrew Holme

The following is the output for a typical session between the Fedora box and Raspberry Pi.

ssh root@192.168.1.2 -vvv OpenSSH_5.5p1, OpenSSL 1.0.0e-fips 6 Sep 2011 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 192.168.1.2 [192.168.1.2] port 22. debug1: Connection established. debug1: identity file /home/lama/.ssh/id_rsa type -1 debug1: identity file /home/lama/.ssh/id_rsa-cert type -1 debug3: Not a RSA1 key file /home/lama/.ssh/id_dsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /home/lama/.ssh/id_dsa type 2 debug1: identity file /home/lama/.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5 debug1: match: OpenSSH_5.5 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.5 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hell man-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-s ha1 debug2: kex_parse_kexinit: snipped-for-privacy@openssh.com,ssh-dss-cert-v00@openssh .com,ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcf our128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,a rcfour, snipped-for-privacy@lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcf our128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,a rcfour, snipped-for-privacy@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1, snipped-for-privacy@openssh.com,hmac-ripem d160, snipped-for-privacy@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1, snipped-for-privacy@openssh.com,hmac-ripem d160, snipped-for-privacy@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none, snipped-for-privacy@openssh.com,zlib debug2: kex_parse_kexinit: none, snipped-for-privacy@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hell man-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-s ha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcf our128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,a rcfour, snipped-for-privacy@lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcf our128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,a rcfour, snipped-for-privacy@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1, snipped-for-privacy@openssh.com,hmac-ripem d160, snipped-for-privacy@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1, snipped-for-privacy@openssh.com,hmac-ripem d160, snipped-for-privacy@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none, snipped-for-privacy@openssh.com debug2: kex_parse_kexinit: none, snipped-for-privacy@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024

Reply to
dakupoto

Check what is in your ssh key file.

My .ssh/id_rsa contains something like this:

-----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,0000000000000000

0sd33kK324234k....

Can you log in using username+password ?

--
mikko
Reply to
Mikko Syrjalahti

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.