Page 1 of 1
Unlocking screen when locked not working in 5.0 rc2
Posted: 13 Oct 2020, 17:04
by dutchkind
I have a timeout set to lock the screen after a certain time but unlocking fails even though the password is correct. Have to kill x to start the session again, then it works with my password (btw I set a custom user password) In rc1 it worked, what I see different is that pam now seems included, is that maybe the cause? I tried some options but couldn't get it to work
Unlocking screen when locked not working in 5.0 rc2
Posted: 13 Oct 2020, 22:28
by ncmprhnsbl
KDE right? what's the permissions on your /etc/shadow file? seems kde's screenlocker needs it to be rw--r--r (which is a security concern... not sure if this is something we've done or a KDE bug)
Unlocking screen when locked not working in 5.0 rc2
Posted: 14 Oct 2020, 07:33
by dutchkind
Yes, KDE, forgot to add that info.
And yes, that fixes it, which is a security risk, I agree, but what I don't understand is that my KDE in Opensuse has the same permissions as the original one in Porteus, even the group owner is the same, and there it works with rw--r----
Unlocking screen when locked not working in 5.0 rc2
Posted: 14 Oct 2020, 12:57
by dutchkind
Not satisfied with a user readable shadows file, I kept searching for a better solution. I found one but don't know about security implications.
I changed the permissions of /usr/lib64/libexec/kcheckpass to 4755 and that solved it.
Unlocking screen when locked not working in 5.0 rc2
Posted: 15 Oct 2020, 03:06
by ncmprhnsbl
dutchkind wrote: ↑14 Oct 2020, 12:57
Not satisfied with a user readable shadows file, I kept searching for a better solution. I found one but don't know about security implications.
I changed the permissions of /usr/lib64/libexec/kcheckpass to 4755 and that solved it.
was thinking along those lines ... looks like (lots of) file permissions got messed up somewhere in the process of tweaking the original build... and indeed, that file should have been rwsr-x--x ..