Bug 575394

Summary: PKINIT fails and krb5kdc service crashes when CRL verification enabled
Product: [Fedora] Fedora Reporter: Roman Kisilenko <rkisilenko>
Component: krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: nalin
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 12:01:22 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Roman Kisilenko 2010-03-20 10:04:19 EDT
Description of problem:
In case KDC is configured to use CRL for PKINIT, PKINIT fails and krb5kdc service crashes.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure KDC and clients to verify CRL for PKINIT.
2. Execute kinit on the client
Actual results:
1. kinit fails to get kerberos ticket
2. krb5kdc service crashes on the server
3. krb5kdc.log contains following records
Mar 16 23:09:36 kerberos.xxx krb5kdc[6717](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) xxx.xxx.xxx.xxx: NEEDED_PREAUTH: user@realm for krbtgt/realm@realm, Additional pre-authentication required
Mar 16 23:09:36 kerberos.xxx krb5kdc[6717](info): preauth (pkinit) verify failure: Different CRL scope
Mar 16 23:09:36 kerberos.xxx krb5kdc[6717](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) xxx.xxx.xxx.xxx: PREAUTH_FAILED: user@realm for krbtgt/realm@realm, Different CRL scope

Expected results:
Kinit should succeed.

Additional info:
CRL is up to date and looks fine. It is produced by dogtag CA and works for other services, e.g. apache httpd.
The problem have appeared after upgrading to Fedora 12, exactly the same configuration in Fedora 11 works fine.
Disabling CRL verification in kdc.conf and krb5.conf is the only workaround I was able to find.
Comment 1 Bug Zapper 2010-11-03 15:05:46 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 2 Bug Zapper 2010-12-03 12:01:22 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.