|
2013-12-17
, 11:38
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#992
|
The Following User Says Thank You to juiceme For This Useful Post: | ||
|
2013-12-17
, 12:44
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#993
|
|
2013-12-21
, 10:54
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#994
|
|
2013-12-21
, 11:15
|
|
Posts: 6,436 |
Thanked: 12,701 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#995
|
The Following User Says Thank You to coderus For This Useful Post: | ||
|
2013-12-21
, 22:24
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#996
|
|
2013-12-23
, 21:27
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#997
|
@Garp you should login as nemo, not root. password set in developer mode settings. to gain root you should use devel-su later.
"ssh -i my_n9_identity root@192.168.2.15"
Just deleting earlier long story just telling:
To get root access in Ubuntu 12.04 (and maybe even 13.10?) in Ubiboot maintenance mode N9, just in Ubuntu Alt-F2 and key-in gksu nautilus then you have root access to all of it!
The Following 2 Users Say Thank You to juiceme For This Useful Post: | ||
|
2013-12-24
, 10:27
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#998
|
@coderus, AFAIK @garp was trying to ssh into ubiboot console, not to Nemo/Sailfish (where the password is "nemo" in some versions...)
There's no password set for root in ubiboot, instead to use ssh/sftp to access ubiboot maintanance console, you need to use keypairs. (this is a security feature really)
To use ssh/sftp to access ubiboot maintanance console, you first have to make private&public keypair with ssh-keygen, then insert your public key into the G_SSH_AUTHORIZED_KEYS key in your ubiboot.conf.
Then, when logging into the device you need to use the private key, just like documented in your ubiboot.conf:
"ssh -i my_n9_identity root@192.168.2.15"
@garp, I do not quite follow up your logic here
Sure you need to create the keypair first, before engaging nautilus login...?
|
2013-12-24
, 19:01
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#999
|
......
root@garp-Lenovo-B590:/home/garp# ssh -i my_n9_identity root@192.168.2.15
Warning: Identity file my_n9_identity not accessible: No such file or directory.
The authenticity of host '192.168.2.15 (192.168.2.15)' can't be established.
......
"ssh -i ~/.ssh/my_n9_identity root@192.168.2.15"
The Following User Says Thank You to juiceme For This Useful Post: | ||
|
2013-12-25
, 15:08
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#1000
|
Could be this reason above ^^
Where do you have the private key "my_n9_identity" ?
when linux says "No such file or directory" it usually means you have not specified where to look for the file in question...
Now I am going to take a really wild guess and say it is in your .ssh/ directory, as that is the customary place to put keys into
So, the reason it works with Nautilus is that it goes and looks for the keys in the default ssh directory, and finds it there.
On command line, you should maybe try something like:
"ssh -i ~/.ssh/my_n9_identity root@192.168.2.15"
Last edited by mirjan79; 2013-12-17 at 11:13.