common-auth still carries nullok #13
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/common#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #12.
/etc/pam.d/common-authon a built core carriespam_unix.so nullok(Debian's default, from/usr/share/pam-configs/unix). #12 removesnullokfrom Webmin's own stack only.On libpam 1.7 (Debian 13), measured with the real module in
tests/pam-unix.bats: through a stack withnullok, an account whose field is empty orU6aMy0wojraho(the crypt of the empty string) is authenticated with any password, without being asked. #12 makes the build write*, which closes that for root, but any other account that ever carries an empty field is open through every service that includes common-auth (login, su, and so on).Removing it is not a
sedoncommon-auth:pam-auth-updateregenerates that file from the profiles on every PAM package upgrade, so the change has to be a profile (or a diverted/usr/share/pam-configs/unix) that survives it, with a test that runspam-auth-updateand asks the real module afterwards.