On 14/10/2020 13:24, Andrei Borzenkov wrote:
On Wed, Oct 14, 2020 at 11:42 AM Thomas HUMMEL <thomas.hummel@xxxxxxxxxx> wrote:
Hello,
thanks for your answer. It's getting clearer.
Still : why would the user crond runs on behalf of needs to be allowed
in access.conf to access the systemd-user service ?
My understanding is that the user@<uid>.service creation needs this
service type (or just the systemd --user creation ?) such a rule in
access.conf is not needed for let's say a ssh login first session ?
Does PAM configuration for SSH include pam_systemd on your system?
Yes, via the password-auth include :
sshd:
session include password-auth
password-auth:
-session optional pam_systemd.so
Thanks
--
Thomas HUMMEL
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
