Bug 3900
Summary: | /lib/security/pam_securetty.so flubs PTS entries under ssh? | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | James E. Leinweber <jiml> |
Component: | pam | Assignee: | David Lawrence <dkl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | clemons |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-07-30 15:37:08 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
James E. Leinweber
1999-07-05 16:10:44 UTC
No, it means that you should not be using securetty with ssh. ptys are insecure except when encrypted, say with ssh, and pam_securetty is doing precisely the right thing. Just take it out of the stack for ssh, unless you do not want root to be able to log in via ssh. :-) |