Re: Fwd: Interacting with PAM issues

* Mikhail Zakharov <zmey20000@yahoo.com> [20230426 08:25]:
> FWD to record the solution in the history of the maillist.
> 
> Exactly what is required, for the exact mentioned purpose of a terminal
> screenlocker application: https://github.com/mezantrop/sclocka. Thank you
> again!

If you create a port of it, consider adding a run dependency to my
little helper and providing a PAM service policy calling it, example is
in the manpage of the port :) (some screen lockers already do that)

Note I consider this whole thing a bug (just like LinuxPAM's workaround
is a bug), but the "sane" solution, providing some authentication
service for the local passwd database that pam_unix could use, would be
a *lot* of work ...

-- 
 Felix Palmen <zirias@FreeBSD.org>     {private}   felix@palmen-it.de
 -- ports committer (mentee) --            {web}  http://palmen-it.de
 {pgp public key}  http://palmen-it.de/pub.txt
 {pgp fingerprint} 6936 13D5 5BBF 4837 B212  3ACC 54AD E006 9879 F231