summaryrefslogtreecommitdiff
path: root/src/home/pam_systemd_home.c
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2020-09-02 16:37:42 +0200
committerLennart Poettering <lennart@poettering.net>2020-09-21 18:02:35 +0200
commit3e0b54867e22523cffda3b80e179df89b6d81bcd (patch)
tree072d8c13477a480752dd6b6b01774a8b28428427 /src/home/pam_systemd_home.c
parent61a29a020c5c6611a22a84c1456e8da7aa656194 (diff)
downloadsystemd-3e0b54867e22523cffda3b80e179df89b6d81bcd.tar.gz
user-record: don't refuse login when last pw change time is in the future
The RTC is like just off, it's a weird system state, let's continue without requiring pw change.
Diffstat (limited to 'src/home/pam_systemd_home.c')
-rw-r--r--src/home/pam_systemd_home.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/home/pam_systemd_home.c b/src/home/pam_systemd_home.c
index db182dc999..8fe52f44aa 100644
--- a/src/home/pam_systemd_home.c
+++ b/src/home/pam_systemd_home.c
@@ -904,6 +904,11 @@ _public_ PAM_EXTERN int pam_sm_acct_mgmt(
(void) pam_prompt(handle, PAM_ERROR_MSG, NULL, "Password will expire soon, please change.");
break;
+ case -ESTALE:
+ /* If the system clock is wrong, let's log but continue */
+ pam_syslog(handle, LOG_WARNING, "Couldn't check if password change is required, last change is in the future, system clock likely wrong.");
+ break;
+
case -EROFS:
/* All good, just means the password if we wanted to change we couldn't, but we don't need to */
break;