News for hackers. Stuff that matters.
Re:The Surreal Horror of PAM (2021) by tbrownaw on Monday October 24, 2022 @10:33PM (#33325481)
So what's a proper way to solve the problem that PAM solves? Instead of an in-process library, have it be a daemon that responds to DBUS requests?

Aside from the config language, this sounds mostly like "it's a pre-login modular C library, and that's alien territory".

Re:The Surreal Horror of PAM (2021) by xena on Monday October 24, 2022 @10:39PM (#33325520)
It would probably need kernel support for this to happen, but I'd like to see a daemon in the system that runs authentication logic and then arbitrarily curses the requesting process with the UID/GID/whatever it needs to get the job done.
Re:The Surreal Horror of PAM (2021) by stevekemp on Tuesday October 25, 2022 @05:18AM (#33328138)
How would that work with, for example a single deamon supporting multiple (different) remote users - for example ftpd, or sshd?

(I imagine you could say that sshd forks for each user, but some of the legacy systems like ftpd/ircd wouldn't have that as an option..)

Re:The Surreal Horror of PAM (2021) by kaba0 on Monday October 24, 2022 @11:57PM (#33326022)
I think Android has a more saner system, but I’m a layperson when it comes to these — android runs every user process under a different user that has very restricted access (restricted with SELinux as well), and they do extensive IPC. There is a daemon that handles elevated requests through IPC, so that’s where dynamic access control happens.