| Summary: | sys-apps/systemd: Missing kernel check for CONFIG_AUDITSYSCALL=y when PAM is enabled | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
| Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=438368 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 438368 | ||
| Bug Blocks: | |||
btw doesn't logind basically require the PAM module? Patched in 206-r1 that I have just committed. The other bug still needs consideration. (In reply to Michał Górny from comment #1) > btw doesn't logind basically require the PAM module? only for logging from 'tty' by eg. startx to X to track the session from tty, to X -> 2 session, 1 inactive from tty, and one active for X but if you use display manager like GDM with native systemd-logind support, then it doesn't use the PAM module -> 1 session, active for X same as in ConsoleKit |
pam_systemd.so needs CONFIG_AUDITSYSCALL=y just like pam_ck_connector.so (from sys-auth/consolekit) needs to get /proc entry of sessionid to track like for 'login -> pam_systemd.so -> tty -> startx -> pam_systemd.so -> X' inherit linux-info pkg_setup() { use pam && CONFIG_CHECK+=" ~AUDITSYSCALL" linux-info_pkg_setup } #systemd, Freenode 20:07 < ssuominen> I maybe have missed the answer if tomegun2 answered it. 20:07 < ssuominen> Does pam_systemd.so use CONFIG_AUDITSYSCALL=y like pam_ck_connector.so did? 20:07 < ssuominen> To get /proc entry of sessionid to track? 20:17 < heftig> ssuominen: it does.