I wonder if this issue could cause an invalid pam configuration to be
generated? In my example, pwquality is a "requisite". But if this
affected a module marked [success=end], seems that it might mess up the
jump offset counts.
Didn't try because I didn't want to deal with having a broken pam
conf
Public bug reported:
If a configuration file in /usr/share/pam-configs has CRLF-style line
endings, pam-auth-update will silently fail with no errors.
I won't suggest that the config should allow CRLF line endings. But if a
file does have alternate line endings, the script should present an
error
2 matches
Mail list logo
