Separate UI for setting a password and enabling SSH connections
In my head, having the ability to accept SSH connections and a having an user password set are two completely separate things:
- I shouldn't need to have a SSH daemon running to set a user password (for use in
devel-su
, for instance), and - I shouldn't need to have a password set to connect via SSH. Currently, if I enable ssh connections but I don't set a password for
nemo
, I cannot log in even with a public key.
Unfortunately, the two things only come together in Jolla, which I think is confusing on multiple levels.
It's more than an inconvenience -- having a password set when you don't need it, or a sshd daemon running when you don't need it, is a security problem.
So, I have a feature request: It should be possible to set a password for user nemo
without activating sshd, and it should be possible to have a running sshd without a password set.
Apologies if it has been asked already; I can find many related discussions but not this exact thing.
Agreed. I found it confusing too but learned to live with it.
pichlo ( 2015-12-31 23:13:26 +0200 )editI agree with you in so far that both options should be handled separately. Wouldn't it be a good idea to set two different passwords in the UI, one for ssh connection as nemo and the other one for root access with devel-su? Actually, you type in the password to connect as nemo via ssh, and then you use the same password again to become root. This doesn't make any sense to me, because it doesn't mean any additional security in comparison to a direct login as root. Sure, you can use ssh keys instead, but shouldn't it work more secure out-of the-box?
By the way, I can always log in with the keys, even if ssh access is disabled. I just haven't managed yet to figure out, why this is possible.
Laura ( 2016-01-02 02:24:35 +0200 )edit