/etc/login.defs documents the LOGIN_STRING option.
This option could be customized like:
LOGIN_STRING "%s's Password: "
to show the username and the Password prompt, as documented.
There are a few different layers calling 'pam_get_authtok', most,
if not all, pass NULL as prompt value. Instead of using a hardcoded
default of 'Password: ', it should parse LOGIN_STRING from
/etc/login.defs. Another option, and also for consistency, maybe
there should also exist a PAM_PASSWORD_PROMPT pair to PAM_USER_PROMPT.
In that case, it could be set by the login program.
I don't think this issue is critical enough to include it in RHEL7. Do you mind if I change it to RHEL8?
By the way, I'm changing the component to shadow-utils, since this is the one handling LOGIN_STRING.
Just a note, shadow-utils documents it, but in the current state (easiest fix) it is pam
that should parse and LOGIN_STRING from /etc/login.defs.
I agree that it should be pam. Moreover, I'm changing product to RHEL8.
After a discussion with upstream (https://github.com/linux-pam/linux-pam/pull/356) I think that it doesn't make much sense to include the LOGIN_STRING functionality in pam. So, I propose to remove the references to LOGIN_STRING from login.defs file, which in turn, means changing the package to shadow-utils.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (shadow-utils bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.