| Summary: | Wrong PAM management group used for pam_nologin in sample files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Iain Morgan <imorgan> | ||||
| Component: | Miscellaneous | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED FIXED | ||||||
| Severity: | normal | CC: | djm | ||||
| Priority: | P2 | ||||||
| Version: | 5.1p1 | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 1481 | ||||||
| Attachments: |
|
||||||
patch applied, will be in 5.2. Thanks again. Close bugs fixed/reviewed for openssh-5.2 release |
Created attachment 1563 [details] Move pam_nologin from auth to account PAM management group The sample PAM configuration files under the contrib/ directory invoke pam_nologin form the auth management group. To ensure that the module is invoked for all authentication methods when PAM is enabled, it should really be called from the account management group instead. The attached patch fixes this.