Bug 478032 – sys-apps/systemd: Missing kernel check for CONFIG_AUDITSYSCALL=y when PAM is enabled

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Samuli Suominen (RETIRED) 2013-07-24 17:22:36 UTC]

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.

[Comment 1 Michał Górny 2013-07-31 21:41:35 UTC]

btw doesn't logind basically require the PAM module?

[Comment 2 Michał Górny 2013-07-31 22:26:46 UTC]

Patched in 206-r1 that I have just committed. The other bug still needs consideration.

[Comment 3 Samuli Suominen (RETIRED) 2013-08-01 10:01:31 UTC]

(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