Sailfish SDK version 1608 (2.0.2) Qt5 released - Page 5 - maemo.org

thedead1440 | # 41 | 2013-02-26, 14:07 | Report

brunelli,

First type "unset SSH_AUTH_SOCK" then type the ssh command. Also ensure the port is free.

luke_dirtwalker | # 42 | 2013-02-26, 14:08 | Report

i think it should be -p 2222 not 2223 ?

brunelli | # 43 | 2013-02-26, 14:15 | Report

Originally Posted by thedead1440 View Post

brunelli,

First type "unset SSH_AUTH_SOCK" then type the ssh command. Also ensure the port is free.

Also results in permission denied :/

Code:

[ian@localhost ~]$ unset SSH_AUTH_SOCK
[ian@localhost ~]$ ssh root@localhost -p 2223 -v -i ~/.ssh/mer-qt-creator-rsa
OpenSSH_6.1p1, OpenSSL 1.0.1c-fips 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 50: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 2223.
debug1: Connection established.
debug1: identity file /home/ian/.ssh/mer-qt-creator-rsa type 1
debug1: identity file /home/ian/.ssh/mer-qt-creator-rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.6
debug1: match: OpenSSH_5.6 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.1
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: 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: Server host key: RSA 4a:96:c8:bb:75:f6:68:64:b6:0c:c1:8a:49:e5:d0:b4
debug1: Host '[localhost]:2223' is known and matches the RSA host key.
debug1: Found key in /home/ian/.ssh/known_hosts:2
debug1: ssh_rsa_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
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/ian/.ssh/mer-qt-creator-rsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).

Originally Posted by luke_dirtwalker View Post

i think it should be -p 2222 not 2223 ?

I think you're right

Code:

[ian@localhost ~]$ ssh root@localhost -p 2222 -v -i ~/.ssh/mer-qt-creator-rsa
OpenSSH_6.1p1, OpenSSL 1.0.1c-fips 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 50: Applying options for *
debug1: Connecting to localhost [127.0.0.1] port 2222.
debug1: Connection established.
debug1: identity file /home/ian/.ssh/mer-qt-creator-rsa type 1
debug1: identity file /home/ian/.ssh/mer-qt-creator-rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.6
debug1: match: OpenSSH_5.6 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.1
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: 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: Server host key: RSA 08:2b:bc:09:14:1b:55:20:27:14:48:57:92:57:fa:5c
debug1: checking without port identifier
The authenticity of host '[localhost]:2222 ([127.0.0.1]:2222)' can't be established.
RSA key fingerprint is 08:2b:bc:09:14:1b:55:20:27:14:48:57:92:57:fa:5c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[localhost]:2222' (RSA) to the list of known hosts.
debug1: ssh_rsa_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
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/ian/.ssh/mer-qt-creator-rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to localhost ([127.0.0.1]:2222).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LC_MONETARY = en_US.utf8
debug1: Sending env LC_NUMERIC = en_US.utf8
debug1: Sending env XMODIFIERS = @im=ibus
debug1: Sending env LANG = en_US.utf8
debug1: Sending env LC_MEASUREMENT = en_US.utf8
debug1: Sending env LC_TIME = en_US.utf8
Last login: Mon Feb 25 12:39:55 2013 from 10.0.2.2
[root@SailfishSDK ~]#

Edit:
From known issues of Sailfish Emulator...

Originally Posted by

- If deployment fails with: "Could not connect to host: Timeout waiting for reply from server." then there is a problem with VirtualBox and DNS resolution. To fix either ssh in to the emulator as root or press right-ctrl+F2 and login as root/nemo. Then echo nameserver 8.8.8.8 > /etc/resolv.conf inside the emulator.
- If you get "Agent admitted failure to sign using the key" when using ssh, try setting SSH_AUTH_SOCK=

Is this related to my problem?

Last edited by brunelli; 2013-02-26 at 14:23.

pycage | # 44 | 2013-02-26, 14:26 | Report

Originally Posted by luke_dirtwalker View Post

i think it should be -p 2222 not 2223 ?

These are different VMs. 2222 is used for connecting to the MerSDK VM where the stuff gets compiled. 2223 is used for connecting to the Sailfish Emulator VM where stuff gets deployed.
In this case, it seems that 2223 is the right one. Check that the VM can access the ssh public key via shared folders.
You can get a terminal in the emulator by pressing Right Ctrl + F2. You can then login as user nemo or root, both with password nemo.
Right Ctrl + F1 brings you back to the UI.

The Following 2 Users Say Thank You to pycage For This Useful Post:
fw190, rcolistete

brunelli | # 45 | 2013-02-26, 14:36 | Report

Originally Posted by pycage View Post

Check that the VM can access the ssh public key via shared folders.
You can get a terminal in the emulator by pressing Right Ctrl + F2. You can then login as user nemo or root, both with password nemo.
Right Ctrl + F1 brings you back to the UI.

Done!
How can I check this? :s

pycage | # 46 | 2013-02-26, 14:42 | Report

Enter mount and watch the output. Is there "ssh" mounted to somewhere? If yes, is the ssh key available (the file with suffix .pub) and readable in that path?

Edit: also check if the ssh daemon is running. Enter "ps -ef | grep sshd" to see if it's running. If not, "systemctl start sshd.service" as root will start it.

Last edited by pycage; 2013-02-26 at 14:44.

The Following User Says Thank You to pycage For This Useful Post:
fw190

murrayy | # 47 | 2013-02-26, 14:47 | Report

Had the same problem. For me, moving the public key out of the way did the trick.
Try:

Code:

 mv ~/.ssh/mer-qt-creator-rsa.pub ~/.ssh/mer-qt-creator-rsa.pub.backup

and then again:

Code:

ssh root@localhost -p 2223 -i ~/.ssh/mer-qt-creator-rsa

EDIT: On your computer, not in the emulator.

The Following User Says Thank You to murrayy For This Useful Post:
rooster13

brunelli | # 48 | 2013-02-26, 14:56 | Report

No ssh on mount, and ssh daemon is running...

shabmanu | # 49 | 2013-02-26, 14:59 | Report

can anyone upload a video of sailfish sdk running on pc to youtube?

pycage | # 50 | 2013-02-26, 14:59 | Report

Originally Posted by brunelli View Post

No ssh on mount, and ssh daemon is running...

Hmm, I don't have the emulator VM at hand right now, but that looks broken to me. Have you modified the configuration of this virtual machine or are you using an old version of VirtualBox, perhaps?