#9: [PATCH] Allow pam_lastlog to write to utmp as an option
-------------------------------------------------+-------------------------
Reporter: shadowkyogre | Owner: pam-
Type: enhancement | developers@…
Priority: major | Status: new
Version: 1.1.x | Component: modules
Keywords: pam_lastlog utmp update patch | Resolution:
prototype | Blocked By:
Blocking: |
-------------------------------------------------+-------------------------
Comment (by shadowkyogre):
Sorry for the long delay on replying. As for why that was the case (for
why I wrote the patch), I wasn't aware that it was the responsibility of
the login program at the time of writing it. It was during a time that I
was testing out developing a login program in python and the python-utmp
library only provided read-access when I was trying to use it to record
utmp entries (which was pretty odd, and I had to rely on sessreg in order
to log the entries reliably) after authenticating the user. Which led me
to fiddling around in pypam to make authenticating easier, but had to
search around various other sources to see how utmp entries were recorded
(including sessreg's source).
As for preserving the default behavior, would it be more sane to assume
that the utmp logging should always be turned off?
--
Ticket URL: <
https://fedorahosted.org/linux-pam/ticket/9#comment:3>
linux-pam <
http://fedorahosted.org/linux-pam>
The Linux-PAM (Pluggable Authentication Modules) project