PAM has a number of attributes that PAM modules can use to log/set useful metadata. E.g. pam_systemd looks at these: PAM_SERVICE PAM_XDISPLAY PAM_TTY PAM_RUSER PAM_RHOST Currently we only set PAM_TTY (and we set it to /dev/thinlinc, which doesn't match the thinlinc/# we give to wtmp). systemd seems to not prefer "fake" tty:s, and has heuristics like looking for ":", so maybe we should reevaluate what we put in there.
Since we ran into bug 5166 I guess we've already implemented PAM_XDISPLAY.
I'm uncertain if there is much to do here: (In reply to Pierre Ossman from comment #0) > PAM has a number of attributes that PAM modules can use to log/set useful > metadata. E.g. pam_systemd looks at these: > > PAM_SERVICE I'm assuming this is set implicitly by PAM. > PAM_XDISPLAY Set since r28882 for bug 5104. > PAM_TTY Set since forever. > PAM_RUSER Not set. I am not certain how interesting it is. > PAM_RHOST Set since r27374 for bug 4644. Set to something bogus, though. See bug 5682. So, I don't see anything valuable for us to set here. Closing until a practical use case pops up.
