https://bugzilla.redhat.com/show_bug.cgi?id=2010528
--- Comment #6 from Björn 'besser82' Esser <[email protected]> --- (In reply to Iker Pedrosa from comment #4) > If you are only planning to use it for your testing that's fine, but I think > it's dangerous to do that in production environments. There can't be any harm, but the pam-tcb package intentionally not being installable when replace_pam_unix is enabled without forcing rpm manually to explictly ignore several arising conflicts. > By the way, what are your plans for replacing pam_tcb in pam stack files? I > think that authconfig should be aware of it and have some configuration to > change between one and the other. And at some point in the future we could > change the default in authconfig from pam_unix to pam_tcb. Just a little > gossip, there's an authconfig SWC in draft to change pam stack files > ownership to this package. Using pam_tcb in the stack files is one part of the change as I have it in mind. I know there are changes needed to authconfig as well, and I think, it's a good idea to coordinate between the different changes and discuss their extends to be as little disruptive as possible. -- You are receiving this mail because: You are always notified about changes to this product and component You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2010528 _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
