Bug 799007

Summary:	pam_krb5 seem to ignore KVNOs in /etc/krb5.keytab
Product:	Red Hat Enterprise Linux 6	Reporter:	Ondrej Valousek <ondrejv>
Component:	pam_krb5	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	dpal, jhrozek, prc
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-09-18 13:55:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	782183, 1002711

Description Ondrej Valousek 2012-03-01 14:34:53 UTC

Description of problem:

When logging in using Kerberos, module pam_krb5.so seems to validate the TGT using system Kerberos database (/etc/krb5.ketab). It usually ends up using the "host/" principal for this checks. This check works fine unless there are more "host/" principals in the system keytab file (for example some process is renewing them creating new principals with a higher KVNO) - in this case, pam_krb5.so seems to pick the first one only and the check will fail with the message like this:

pam_krb5[27045]: TGT failed verification using keytab and key for
'host/draco.prague.s3group.com.S3GROUP.COM': Wrong principal in
request

and the user login attempt is rejected.


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

How reproducible:
always

Comment 2 RHEL Program Management 2012-07-10 08:16:24 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2012-07-11 01:53:10 UTC

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 5 RHEL Program Management 2012-09-07 05:31:31 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2013-10-14 00:47:27 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 9 Chris Williams 2015-09-18 13:55:58 UTC

This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6 and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.