Active Topics

 



Notices


Reply
Thread Tools
Posts: 146 | Thanked: 15 times | Joined on Oct 2008
#1
Hi all,
Finally my N800 arrived!! Beautiful gadget, that seems to run quite well.

I have a very silly question. I searched around and googled, but was unable to find the answer (probably because the question is too silly).

I installed both SSH client and server, the SSH server specially to allow me to use my PC keyboard. I was able to ssh my PC with no problems. But when trying to ssh my N800, I get:
$ ssh root@147.65.21.102
root@147.65.21.102's password: *********
Permission denied, please try again.

Same result using user as user.

What am I doing wrong?

Thanks!
L.
 
qwerty12's Avatar
Posts: 4,274 | Thanked: 5,358 times | Joined on Sep 2007 @ Looking at y'all and sighing
#2
You're entering the correct password? You installed openssh-server, not dropbear right? If you installed openssh, it should have asked you to set the password.

sshing in as user won't work; user has no password (although, I believe, for OpenSSH, you can edit sshd.conf to allow login to accounts with empty passwords). You can set one but I usually "su - user" after sshing in as root.

If you need to set the root password, install rootsh from application manager; run "root" and run "passwd".

Last edited by qwerty12; 2009-04-08 at 14:50.
 
Posts: 146 | Thanked: 15 times | Joined on Oct 2008
#3
Originally Posted by qwerty12 View Post
You're entering the correct password?
I think so...

You installed openssh-server, not dropbear right?
Right.

If you installed openssh, it should have asked you to set the password.
It did.

sshing in as user won't work; user has no password.
I set user password with passwd command.

You can set one but I usually "su - user" after sshing in as root.
I see.

If you need to set the root password, install rootsh from application manager; run root and run passwd.
I did it again, same problem. The third incorrect password gave me:

Permission denied (publickey,gssapi-with-mic,password).

Thanks!

L.
 
jeremiah's Avatar
Posts: 170 | Thanked: 261 times | Joined on Feb 2009 @ Gothenburg, Sweden
#4
Can you run your ssh command with the -vv switch? This produces more verbose output and might help diagnose the problem.

i.e. `ssh -vv me@somewhere.com`
 
Posts: 146 | Thanked: 15 times | Joined on Oct 2008
#5
Originally Posted by jeremiah View Post
Can you run your ssh command with the -vv switch? This produces more verbose output and might help diagnose the problem.

i.e. `ssh -vv me@somewhere.com`
Sure. Here you are:

$ ssh -vv root@147.65.21.102
OpenSSH_4.7p1, OpenSSL 0.9.8b 04 May 2006
debug1: Reading configuration data /home/gato/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 147.65.21.102 [147.65.21.102] port 22.
debug2: fd 3 setting O_NONBLOCK
debug1: fd 3 clearing O_NONBLOCK
debug1: Connection established.
debug1: identity file /home/gato/.ssh/identity type -1
debug1: identity file /home/gato/.ssh/id_rsa type -1
debug1: identity file /home/gato/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7
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-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@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-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
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-cbc hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 120/256
debug2: bits set: 518/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '147.65.21.102' is known and matches the RSA host key.
debug1: Found key in /home/gato/.ssh/known_hosts:36
debug2: bits set: 511/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /tmp/lachagaar.id (0xb9794328)
debug2: key: /home/gato/.ssh/identity ((nil))
debug2: key: /home/gato/.ssh/id_rsa ((nil))
debug2: key: /home/gato/.ssh/id_dsa ((nil))
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Offering public key: /tmp/lachagaar.id
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Trying private key: /home/gato/.ssh/identity
debug1: Trying private key: /home/gato/.ssh/id_rsa
debug1: Trying private key: /home/gato/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
root@147.65.21.102's password:
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
Permission denied, please try again.
root@147.65.21.102's password:
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
Permission denied, please try again.
root@147.65.21.102's password:
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey,gssapi-with-mic,password).


Thanks again,
L.
 
Posts: 146 | Thanked: 15 times | Joined on Oct 2008
#6
Please forget about this thread. There was some problem at my work with the network traffic. At home everything worked perfectly.

Thanks!!!!!

L.

Last edited by luis; 2009-04-09 at 01:14.
 

The Following User Says Thank You to luis For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 19:13.