Package: cron Version: 3.0pl1-130 Severity: normal File: /etc/pam.d/cron Hi,
I'm wondering if the cron PAM service shouldn't call the pam_systemd module as well. Looking at RHEL7 it seems that they are doing it. The rational is that if the user wants to run some scripts using the XDG_RUNTIME_DIR directory or D-Bus, we are sure that the directory is present or the broker is started. Not doing this might create difference between the case where the user is logged-in and the case where the user is not. Kind regards, Laurent Bigonville -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages cron depends on: ii adduser 3.118 ii debianutils 4.8.6 ii dpkg 1.19.0.5+b1 ii libc6 2.27-6 ii libpam-runtime 1.1.8-3.8 ii libpam0g 1.1.8-3.8 ii libselinux1 2.8-1+b1 ii lsb-base 9.20170808 Versions of packages cron recommends: ii dma [mail-transport-agent] 0.11-1+b1 Versions of packages cron suggests: ii anacron 2.3-24 pn checksecurity <none> ii logrotate 3.14.0-4 Versions of packages cron is related to: pn libnss-ldap <none> pn libnss-ldapd <none> pn libpam-ldap <none> pn libpam-mount <none> pn nis <none> pn nscd <none> -- no debconf information
diff -u cron-3.0pl1/debian/cron.pam cron-3.0pl1/debian/cron.pam --- cron-3.0pl1/debian/cron.pam +++ cron-3.0pl1/debian/cron.pam @@ -21,0 +22,4 @@ +# Open a logind session +# Doing so will ensure that the XDG_RUNTIME_DIR is exported and the associated +# directory is created. +-session optional pam_systemd.so
