Bug#739676: systemd-user PAM config breaks some libpam-* modules

[Martin Pitt]

Hey Christian,

Christian Kastner [2014-12-28 21:55 +0100]:
>   Trying to run as a user instance, but $XDG_RUNTIME_DIR is not set.
> 
> I assume that this is because common-session also includes
> pam_systemd.so, whereas -noninteractive does not, so switching to the
> latter drops it from systemd-user's config.

Right, libpam_systemd is responsible for both starting a logind
session for it as well as setting up the per-user runtime dir and env
variables like the above.

>   2. Re-add pam_systemd.so to systemd-user's config.
> 
> The attached, updated patch implements 2. I tested it locally, and all
> issues raised so far were resolved.

Thanks for this!

On both my Debian sid and my Ubuntu system, the only difference
between common-session and common-session-noninteractive is that the
latter does not include libpam-systemd. Thus on a system which does
*not* use any additional pam module, this should effectively be a
no-op change and thus quite safe.

Indeed installing libpam-mount only adds itself to common-session, not
to common-session-noninteractive. So with this change we would get the
desired effect.

login, ssh, lightdm etc. all include common-session, so this should be
fine.

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150121/2c109e95/attachment-0002.sig>