You are not logged in.
Pages: 1
Hi,
I cloned this fork of the original vlock so I could use vlock to lock my X session https://github.com/WorMzy/vlock. Unfortunately, I can't authenticate. If I type my password I get an authentication failure. I've also tried using the default vlock to no avail.
In journalctl I see the below error:
pam_warn(vlock:auth): function=[pam_sm_authenticate] flags=0 service=[vlock] terminal=[pts/0] user=[user] ruser=[<unknown>] rhost=[<unknown>]I've search everywhere for someone who has had this issue but don't seem to be getting anywhere. Any ideas?
Offline
No ideas on this end but source does look 6 years old. In most cases this will indicate that a project is no longer maintained and hence very likely to be buggy.
Other than that, if you cared to help me delicate your setup, pair debugging would at least mean some company if not result in the solution to your issue.
Offline
The maintainer is a mod on this forum… enjoy your ban :-P
Offline
Oh blimey, I uploaded that after the original source disappeared and someone on a mailing list asked if anyone had a copy. It's a static copy, to call me a maintainer would be grossly overstating my involvement with the code.
What OP's issue is, is likely that there isn't a PAM configuration file for vlock. You'll need to create one at /etc/pam.d/vlock.
However, there may be an active fork of vlock now, my mirror of an ancient version should be a last resort.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Oh blimey, I uploaded that after the original source disappeared and someone on a mailing list asked if anyone had a copy. It's a static copy, to call me a maintainer would be grossly overstating my involvement with the code.
What OP's issue is, is likely that there isn't a PAM configuration file for vlock. You'll need to create one at /etc/pam.d/vlock.
However, there may be an active fork of vlock now, my mirror of an ancient version should be a last resort.
Thanks for that. I will have a look around.
EDIT: It seems physlock is a more modern alternative.
Last edited by chra (2019-05-11 12:35:51)
Offline
Pages: 1