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.

Bug 1933927

Summary:	ssh login with pam_faillock doesn't display "Account temporarily locked due to %d failed logins".
Product:	Red Hat Enterprise Linux 8	Reporter:	Muneaki Sugaya <msugaya>
Component:	openssh	Assignee:	Jakub Jelen <jjelen>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.3	Flags:	pm-rhel: mirror+
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-02 12:23:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Jakub Jelen 2021-03-02 12:23:28 UTC

There is no API in the SSH protocol to give more information about failed password authentication attempts when using normal password authentication:

https://tools.ietf.org/html/rfc4252#section-8

https://tools.ietf.org/html/rfc4252#section-5.1

The PAM messages should be visible in case the ChallengeResponseAuthentication is used (normal PasswordAuthentication should be disabled in that case). This allows the PAM to communicate additional messages with the client. It is described in the following RFC:

https://tools.ietf.org/html/rfc4256

How to test it:

 * Modify sshd_config to have

    ChallengeResponseAuthentication yes
    PasswordAuthentication no

 * Restart sshd

    systemctl restart sshd

 * Try to connect with the test user:

    # ssh testuser@localhost
    The account is locked due to 3 failed logins.
    (9 minutes left to unlock)
    Password: