Date: Wed, 26 Apr 2023 20:00:57 +0200 From: Mikhail Zakharov <zmey20000@yahoo.com> To: Felix Palmen <zirias@FreeBSD.org>, freebsd-hackers@FreeBSD.org Subject: Re: Fwd: Interacting with PAM issues Message-ID: <2efa7d42-7664-d71b-d56d-8e5336729174@yahoo.com> In-Reply-To: <upvxpposbk7c3cd77avkhwk5tmwqfhndxfd2zgkdqgfovav2gh@k73vpgydlj3j> References: <31aa9f0f-44d9-fb61-2eb3-36af63ce9ed7@yahoo.com> <9e35b8cb-e5de-bdb5-c2da-cee44e18683c@yahoo.com> <upvxpposbk7c3cd77avkhwk5tmwqfhndxfd2zgkdqgfovav2gh@k73vpgydlj3j>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Felix, The port is the thing to do, but for now I've made a note and a reference to your selfauth-helper in the readme: https://github.com/mezantrop/sclocka/blob/master/README.md Best, M On 4/26/2023 7:50 PM, Felix Palmen wrote: > * 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 ... >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2efa7d42-7664-d71b-d56d-8e5336729174>