Bug 231136

Summary: [PATCH]: use 2b-style AFS tickets even if KerberosIV support is enabled
Product: Red Hat Enterprise Linux 4 Reporter: Jan Iven <jan.iven>
Component: pam_krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED DEFERRED QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-15 20:46:53 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: 249559    
Attachments:
Description Flags
new option "prefer_2b" none

Description Jan Iven 2007-03-06 14:11:55 UTC 
We see several unsuccessful attempts for AFS service tickets on our KDC per
login, and are trying to reduce these. Our AFS tickets are of the form
"afs" (i.e. no AFS cell as the instance).

The patch adds a new private option "prefer_2b":

Even with Kerberos IV-support enabled, still try to use the 2b-style
service tickets based on KerberosV instead of using the
KerberosIV-based ones. 

This is the equivalent of giving "-5" to the afs5log command. The effect is to
reduce the number of failed attempts from 9 to 3 (different encoding types are
tried for realm-instance tickets, patch for that follows as well).

The patch is against 2.2.8, I can rework it against other versions if required.

Best regards
Comment 1 Jan Iven 2007-03-06 14:11:55 UTC 
Created attachment 149335 [details]
new option "prefer_2b"
Comment 2 RHEL Program Management 2007-07-06 18:06:16 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 3 Nalin Dahyabhai 2008-02-15 20:46:53 UTC 
When rxk5 becomes available, we're going to have three different ways for
formatting tokens, and at that point I don't think boolean options are going to
provide enough flexibility to set the preferred order in which the various
methods should be tried.  I'm working this out in the development stream, but I
doubt it'll make sense to backport the result to pam_krb5's 2.1 branch. 
Deferring this -- the whole rxk5 thing'd have to be sorted out in RHEL 5 before
I'd feel confident about adding changing RHEL 4.