Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conditionally manage pwhistory.conf and certain parameters in pwquality.conf #145

Closed
michael-riddle opened this issue Jan 30, 2024 · 0 comments · Fixed by #146
Closed

Conditionally manage pwhistory.conf and certain parameters in pwquality.conf #145

michael-riddle opened this issue Jan 30, 2024 · 0 comments · Fixed by #146
Assignees

Comments

@michael-riddle
Copy link
Member

michael-riddle commented Jan 30, 2024

When we ask for any pwhistory values to be controlled, it simply goes directly onto the corresponding lines in /etc/pam.d/system-auth and /etc/pam.d/password-auth. We need a parameter to move those parameters into the correct files. We also need to ensure that el 7 machines do NOT do that even if those parameters are set.

@michael-riddle michael-riddle self-assigned this Jan 30, 2024
michael-riddle added a commit to michael-riddle/pupmod-simp-pam that referenced this issue Feb 5, 2024
michael-riddle added a commit that referenced this issue Feb 6, 2024
* (#145) Added the ability to control pwhistory.conf

Fixes #145

* Updated major version, README, and CHANGELOG

* Minor updates to the README, and removed incorrectly added .err files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant