![]() |
2013-02-26
, 14:08
|
Posts: 105 |
Thanked: 307 times |
Joined on Aug 2012
|
#42
|
![]() |
2013-02-26
, 14:15
|
Posts: 54 |
Thanked: 208 times |
Joined on Oct 2011
@ Brazil
|
#43
|
brunelli,
First type "unset SSH_AUTH_SOCK" then type the ssh command. Also ensure the port is free.
[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).
[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 ~]#
- 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=
![]() |
2013-02-26
, 14:26
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#44
|
The Following 2 Users Say Thank You to pycage For This Useful Post: | ||
![]() |
2013-02-26
, 14:36
|
Posts: 54 |
Thanked: 208 times |
Joined on Oct 2011
@ Brazil
|
#45
|
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.
![]() |
2013-02-26
, 14:42
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#46
|
The Following User Says Thank You to pycage For This Useful Post: | ||
![]() |
2013-02-26
, 14:47
|
Posts: 6 |
Thanked: 1 time |
Joined on Sep 2012
|
#47
|
mv ~/.ssh/mer-qt-creator-rsa.pub ~/.ssh/mer-qt-creator-rsa.pub.backup
ssh root@localhost -p 2223 -i ~/.ssh/mer-qt-creator-rsa
The Following User Says Thank You to murrayy For This Useful Post: | ||
![]() |
2013-02-26
, 14:56
|
Posts: 54 |
Thanked: 208 times |
Joined on Oct 2011
@ Brazil
|
#48
|
![]() |
2013-02-26
, 14:59
|
Posts: 33 |
Thanked: 17 times |
Joined on Jun 2012
|
#49
|
![]() |
2013-02-26
, 14:59
|
|
Posts: 3,404 |
Thanked: 4,474 times |
Joined on Oct 2005
@ Germany
|
#50
|
First type "unset SSH_AUTH_SOCK" then type the ssh command. Also ensure the port is free.