Bug 740806
Summary: | sshd should warn that connection will be dropped after expired password change | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | David Juran <djuran> |
Component: | openssh | Assignee: | Petr Lautrbach <plautrba> |
Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | dapospis, mvadkert, myllynen, pvrabec, sgallagh, ssorce, tmraz |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-29 11:51:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Juran
2011-09-23 12:18:25 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This is impossible. The ssh in the password-authentication method has to use passwd which is explicitly executed after the session is started. Unfortunately there is no exact way to be sure that the user really changed the password in the passwd command so the openssh must force the user to reconnect. I suggest the customer to use keyboard-interactive authentication as a workaround. Sorry Tomas, but I don't get it, why is it that ssh can't use the pam stack (which I believe will give you a better error reporting) and has to run passwd instead ? If it *has* to drop the connection can you make ssh at least warn the user it will be disconnected after the password change ? Yeah the warning could be added before the passwd is executed. It could probably use the pam stack however it would require substantial changes to how the pam stack is called in sshd. Basically it could probably call the PAM calls that are called by passwd directly instead of passwd but I am not sure whether it would not interfere with other things in the SSH protocol anyway so it would have to drop the connection regardless of that. But the warning seems like something that could be easily done. Ok in this case I am reopening this bug. Feel free to defer it for the pam stack portion, but I think we should get at least the warning part. Changing the summary accordingly. Setting qe_test_coverage‑. There is nothing to test. |