Is it possible to set up a passwordless login on Leap 42.2 on a single account?
Things done to date:
sudo passwd -d <username>
Yast->Security and Users->User and Group Management->Expert Options->Passwordless Logins selected for username.
At the login screen when I hit return with empty password all I get is login failure. Thanks in advance for any help.
You are best having an actual password.
And then setup autologin, so that you are logged in on boot without being asked for a password.
You can set that up with:
Yast → System → /etc/sysconfig editor
Desktop → Display manager → DISPLAYMANAGER_AUTOLOGIN
Nothing of value held on the machine. More of games machine used by an elderly relatives, want its use to be as simple as possible (i.e. no passwords to remember).
Did you read (and try) nrickerts advice? Autologin (in the GUI) is passwordless.
Yes, auto-login does work; but to get from the auto-login account to another account you have to logout to login again; appears to be much more straight forward to select the login account and hit return. I had 13.2 set-up as described, but I haven’t been able to replicate the set-up under Leap 42.2.
OK, when I understand you now, you want to have passwordless login in the GUI for more then one user. That was not very clear, at least to me, from your first post.
Thus, such a user types his username in the username field and then sends off the login with an empty password field and that should give him/her a login.
Yes, that is the use-case.
Ok. It is of course not something many people have on their systems, thus I assume not many have a ready answer (well it may be the case that a positive surprise will be posted :)). So we have to test and try.
Did you try if your passwordless setup works for the CLI? E.g. Ctrl-Alt-F1 and type the username and an empty password. That will give at least the idea that a passwordless login is basically possible and configured as such.
To make passwordless login possible, you need to allow empty passwords in the PAM config.
This should do:
sudo pam-config --add --nullok
Thanks wolfi, the PAM configuration was the missing ingredient.