Thread: devel-su and SSHD (developer mode remote connection) on Sailfish
View Single Post
Feathers McGraw's Avatar
Feathers McGraw is offline Feathers McGraw
2016-02-14 , 20:32
Posts: 654 | Thanked: 2,368 times | Joined on Jul 2014 @ UK
#4
Originally Posted by mced View Post
III: My 3G provider, Yoigo (Telia Sonera) gives IPs behind a CGNAT. So the SSH daemon is not accesible to the whole world. Of course, there are these WhatsApp teenagers behind the same CGNAT as me, but I don't expect them to know what SSH means.

IV: The same thing with public wifi's at restaurants, transport and the like.
I'm really surprised to hear someone on this forum make an argument like this. Do you always rely on other peoples' incompetence for the security of your systems?

V: Get root access in 30 seconds? Could you post a link to this bug?
  1. pick up a jolla
  2. enable developer mode
  3. toggle remote connection and set whatever password you like, without having to know the current password
  4. open fingerterm
  5. use devel-su with the password you just set to run commands as root

You shouldn't be able to set the password required for root access like that, it's stupid. On a normal system, if you log in as a user in the sudo group, you need to know either that user's password or the root password to run commands as root (depending on how sudo is configured). If you want to change your own password, you need to know the current password.

VI: I don't know why, but I'm unable to set RSA key authentication on my Jolla. I've got three of four Debian machines, my Raspbian RPi and an OpenWRT router, all of them sharing their respective RSA keys: they work flawlessly. But when it's time to log into my Jolla this way, "Permission denied (publickey)".
Works fine here:

Code:
sam@T440s:~$ ssh-copy-id nemo@192.168.1.227
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
nemo@192.168.1.227's password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh 'nemo@192.168.1.227'"
and check to make sure that only the key(s) you wanted were added.

sam@T440s:~$ ssh nemo@192.168.1.227
Enter passphrase for key '/home/sam/.ssh/id_rsa': 
Last login: Sun Feb 14 20:22:17 2016 from 192.168.1.112
,---
| SailfishOS 2.0.1.7 (Taalojärvi) (armv7hl)
'---
I don't think I had to enable publickey authentication, pretty sure the default configuration allows it.
 

The Following 4 Users Say Thank You to Feathers McGraw For This Useful Post: