Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
/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.
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.
https://access.redhat.com/errata/RHBA-2021:4417