Revision history [back]

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.

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.

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.

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.