Bug 1810328 - pam_krb5 not present in F32
Summary: pam_krb5 not present in F32
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pam_krb5
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Robbie Harwood
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-05 00:37 UTC by Trever Adams
Modified: 2020-03-05 16:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-05 16:36:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Trever Adams 2020-03-05 00:37:17 UTC
Description of problem:
pam_krb5 appears to never have been built for Fedora 32. I do not know if this is an oversight or deliberate decision. It is not present in the acecpted changes for F32, I am doing searches to find it if was oprhaned/retired and can find no such messages in the mailing lists.

I use this quite a bit.

Comment 1 Robbie Harwood 2020-03-05 16:36:44 UTC
pam_krb5 was intentionally orphaned.  I'm not sure why you can't find messages about that; it was done through normal Fedora process.

My intent is for users to migrate to sssd.  I wrote a guide for doing this at https://docs.pagure.org/SSSD.sssd/users/pam_krb5_migration.html  If you need additional assistance, sssd folks can be reached at freenode/#sssd or sssd-users.org https://lists.fedorahosted.org/admin/lists/sssd-users.lists.fedorahosted.org/

Orphaning was done because sssd subsumes the functionality, and unlike pam_krb5 is actually maintained.  While I can't stop you picking it up yourself again, you should know that the old pam_krb5 upstream we were using is no longer active, and pam_krb5 isn't shipped in EL either.


Note You need to log in before you can comment on or make changes to this bug.