Problem SSH'ing into N950?

[MasterZap]

I have problem SSH'ing into the N950, any ideas? No problem into N900. I can SSH "root@localhost" on the N950 itself, but trying from external machine to SSH, I get the password prompt, I type in the password (yes, properly), and it just re-displays the password prompt with no further comment, ad infinitum.

Anyone know what gives?

/Z

[divanov]

It sounds like you are trying to login with wrong password or to wrong host (or both in extreme case).

[MasterZap]

Eh... no. I said so already

If I am on the N950, I can do

ssh root@localhost

or

But if I am on an other device (even my good old N900) and I try to

ssh root@[ip-of-n950]

....I get the failure. And yes, it's the right IP, and yes, it is the right password. I'm not completely dumb

/Z

[divanov]

Try ssh -v

[MasterZap]

OpenSSH_5.1p1 Debian-6.maemo5, OpenSSL 0.9.8n 24 Mar 2010
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 20.100.100.130 [20.100.100.130] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-2+harmattan28+0m6
debug1: match: OpenSSH_5.1p1 Debian-2+harmattan28+0m6 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-6.maemo5
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
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
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '20.100.100.130' is known and matches the RSA host key.
debug1: Found key in /root/.ssh/known_hosts:4
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
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: Trying private key: /root/.ssh/identity
debug1: Trying private key: /root/.ssh/id_rsa
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: password
root@20.100.100.130's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
root@20.100.100.130's password:

[kypeli]

Is developer mode on? Is the SDK Connection (the app in the grid) selected to be USB or WLAN? If yes to both, then I don't have a clue... Works for me...

[MasterZap]

Is developer mode on? Is the SDK Connection (the app in the grid) selected to be USB or WLAN? If yes to both, then I don't have a clue... Works for me...

Huh, what is the "SDK connection" and what does it have to do with SSH'ing into the device?

But okay, I tried, not sure how I turn that "on", but it gave me a (different) password (not the one I set on my root account), but it doesn't help and I can't log in with that either.

You didn't do any trickery with SSH keys or other things? It seems to want a public/private key pair... but the way I understand it a password sohuld also work?

/Z

[kypeli]

Huh, what is the "SDK connection" and what does it have to do with SSH'ing into the device?

I don't know what it actually does - maybe nothing, but at least it will show you the WLAN IP address so you can SSH over WiFi

But okay, I tried, not sure how I turn that "on", but it gave me a (different) password (not the one I set on my root account), but it doesn't help and I can't log in with that either.

You didn't do any trickery with SSH keys or other things? It seems to want a public/private key pair... but the way I understand it a password sohuld also work?

So which username + password combo are you using? root / rootme is the root login credentials that work for me. From there you can do "su - user" to become a normal user. Qt Creator will use the "developer" account to install the packages from Qt Creator on to the device, but I always SSH in as root.

[MasterZap]

I don't know what it actually does - maybe nothing, but at least it will show you the WLAN IP address so you can SSH over WiFi

The IP I know already.

So which username + password combo are you using? root / rootme is the root login credentials that work for me. From there you can do "su - user" to become a normal user. Qt Creator will use the "developer" account to install the packages from Qt Creator on to the device, but I always SSH in as root.

Done all that, and I'm using "root / rootme" altohugh I changed the password on the device from "rootme" to something else, so I am using that other thing, not actually "rootme", but yeah, the root pwd of the device, user name root. Keep getting it.

Maybe I should just reset the device from scratch and try again.....

Sigh, I'm a bit depressed I really wanted to play around with this thing, but it seems stupid trivial obstacles are in my way for some reason.

/Z

[divanov]

Create another account on the device and try to login with its credentials
http://linux.die.net/man/8/useradd

[hartti]

And you followed the instructions in here http://library.developer.nokia.com/t...ttan_85c9.html ?

Hartti

[MasterZap]

SOLVED IT: A fellow Linux guru told me to look in /etc/ssh/sshd_config and lo and behold, there is limiting to the SSH to certain networks, and yes, I use a very peculiar IP range in my house, NOT one of the ones listed as "okay" in the config file... solved!!

To explain, the N950 is set up to only enjoy SSH:ing into it when it's in one of the "private" ip range of e.g. 10.*.*.* or 192.168.*.* for example; I use neither, so it broke.

/Z

[hartti]

Thanks for the tip!

Hartti