search for: xdg_session_class

...n code that currently > > doesn't get them, is that PAM modules session code is privileged, so extra > > care should be taken not to forward there accidentally any environment > > variables that could affect that privileged code in an unintended way. > > > > While XDG_SESSION_CLASS and XDG_SESSION_TYPE variables mentioned by Michal > > are harmless, those LC_* variables AcceptEnv'ed in many default setups are > > also likely to be OK, allowing arbitrary variables listed in AcceptEnv > > could be risky given that some PAM session modules like pam_namespac...

...nd the PAM modules session code that currently > doesn't get them, is that PAM modules session code is privileged, so extra > care should be taken not to forward there accidentally any environment > variables that could affect that privileged code in an unintended way. > > While XDG_SESSION_CLASS and XDG_SESSION_TYPE variables mentioned by Michal > are harmless, those LC_* variables AcceptEnv'ed in many default setups are > also likely to be OK, allowing arbitrary variables listed in AcceptEnv > could be risky given that some PAM session modules like pam_namespace and > pam_...

Hello everyone, I am trying to adjust the systemd-logind classification of the SSH session opened by Ansible client. By default the SSH session created by Ansible client is Class=user and Type=tty in systemd-logind. pam_systemd.so allows users to change this default via the environment variables XDG_SESSION_CLASS and XDG_SESSION_TYPE. When I set these variables on the client and make sure they are accepted by the server I observe in the log that variables are set but that happens *after* PAM session is created in the child process. Hence I have two obvious questions... Is my analysis correct and thus it is...

...am trying to adjust the systemd-logind classification of the SSH > session opened by Ansible client. By default the SSH session created > by Ansible client is Class=user and Type=tty in systemd-logind. > pam_systemd.so allows users to change this default via the environment > variables XDG_SESSION_CLASS and XDG_SESSION_TYPE. When I set these > variables on the client and make sure they are accepted by the server > I observe in the log that variables are set but that happens *after* > PAM session is created in the child process. Hence I have two obvious > questions... > > Is my a...

...am trying to adjust the systemd-logind classification of the SSH > session opened by Ansible client. By default the SSH session created > by Ansible client is Class=user and Type=tty in systemd-logind. > pam_systemd.so allows users to change this default via the environment > variables XDG_SESSION_CLASS and XDG_SESSION_TYPE. When I set these > variables on the client and make sure they are accepted by the server > I observe in the log that variables are set but that happens *after* > PAM session is created in the child process. Hence I have two obvious > questions... > > Is my a...