From ea1ad5e7260c770b21e547702b1e0acef9e4854c Mon Sep 17 00:00:00 2001
From: Karel Zak <kzak@redhat.com>
Date: Thu, 2 Feb 2023 14:52:35 +0100
Subject: lslogins: (man) explain password statuses

Upstream: http://github.com/util-linux/util-linux/commit/95ea3dd4128b625ab12691229020ebc50d578e71
Upstream: http://github.com/util-linux/util-linux/commit/8001bffb03eda8d23d6a04a5dc1469cce932ae36
Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=2159544
Signed-off-by: Karel Zak <kzak@redhat.com>
---
 login-utils/lslogins.1 | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/login-utils/lslogins.1 b/login-utils/lslogins.1
index c831739d9..5c327caf5 100644
--- a/login-utils/lslogins.1
+++ b/login-utils/lslogins.1
@@ -116,6 +116,24 @@ Delimit user entries with a nul character, instead of a newline.
 
 .SH NOTES
 The default UID thresholds are read from /etc/login.defs.
+.SS "Password status"
+.sp
+Multiple fields describe password status.
+.sp
+\fB"Login by password disabled"\fP
+.RS 4
+\*(Aqyes\*(Aq means that there is no valid password. The password hash is missing, or the hash method is unknown or contains invalid chars.
+.RE
+.sp
+\fB"Password not required (empty)"\fP
+.RS 4
+The password is not set (hash is missing); this is common for locked system accounts. Not requiring a password does not mean the user can log\-in without a password. It depends on the password "lock" status.
+.RE
+.sp
+\fB"Password is locked"\fP
+.RS 4
+The password is prefixed by \*(Aq!!\*(Aq, and the user cannot login although the password is set or empty. This is common for new accounts without a set password.
+.RE
 
 .SH EXIT STATUS
 .TP
-- 
2.39.1