Re: [dev] [slock] Compile-Time Pluggable Authentication Code (passwd, pam, etc.)

2024-10-07 Thread Sebastian J. Bronner
Hi Laslo, > > Also think > > about providing a better abstraction, e.g. a possibility for the > > backends to have a void 'state' pointer that they can set up during > > initialisation. In this way, the passwd backend could store the entered > > password in this state (which might as well also be

Re: [dev] [slock] Compile-Time Pluggable Authentication Code (passwd, pam, etc.)

2024-10-06 Thread Sebastian J. Bronner
Hi Страхиња, On Fri, Oct 04, 2024 at 02:33:22PM GMT, Страхиња Радић wrote: > Дана 24/10/04 07:36AM, Sebastian J. Bronner написа: > > Fixed. I had never heard of config.mk before this. A also was not > > able to find any documentation mentioning it anywhere. But I put it >

Re: [dev] [slock] Compile-Time Pluggable Authentication Code (passwd, pam, etc.)

2024-10-03 Thread Sebastian J. Bronner
Hi Laslo, thank you for your feedback. I applied some of it straight away and packed the updated code into another tarball under https://sbronner.com/~waschtl/slock-1.5-waschtl-modular2.tar.gz I split your feedback into 10 points which I will respond to one at a time: > Regarding the code struc

[dev] [slock] Compile-Time Pluggable Authentication Code (passwd, pam, etc.)

2024-09-20 Thread Sebastian J. Bronner
Hi everybody, after using slock for quite some time and being generally very pleased with it, I wanted to use it in more situations, especially ones using PAM. I checked out the patches on the wiki and found them ... incomplete. Depending on what PAM is authentication against, like a fingerprint r