Update to Fedora 42 breaks long-standing PAM configuration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I updated a number of lab computers, and I found Fedora 42 broke their
long-standing PAM configuration. I submitted a Bugzilla ticket here:

https://bugzilla.redhat.com/show_bug.cgi?id=2366249

The problem seems to be related to pam_access, which we use. Downgrading
to the Fedora 41 packages fixes the failed logins. I am not yet sure
what the problem is, but there were some changes in pam_access and
related to the LOCAL keyword.

I suspect I will have to trace some source code to figure this out. Has
anyone else had problems with PAM on Fedora 42?

-- 
Mike

:wq
-- 
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux