referrals in 1.6

Jeffrey Hutzelman jhutz at cmu.edu
Wed Feb 28 11:39:45 EST 2007



On Tuesday, February 27, 2007 09:31:35 AM -0600 Nicolas Williams 
<Nicolas.Williams at Sun.COM> wrote:

> On Tue, Feb 27, 2007 at 09:08:07AM -0500, Jeffrey Altman wrote:
>> Mark Phalan wrote:
>> >>     Mark> 02/23/07 06:55:18  02/23/07 16:53:42  host/z4.acme.com@
>> >>     Mark>         renew until 02/24/07 06:53:42
>> >>     Mark>
>> >>     ^^^^^^^^^^ Mark>
>> >>     No Realm. Mark> Is this expected behaviour?
>> >>
>> >> Yes.  If you do anything else, you won't cache the resulting
>> >> principal.
>> >
>> > Ok, makes sense. It is however slightly confusing when referrals are
>> > NOT used.
>>
>> Would it have been less confusing if the name of the service principal
>> were:
>>
>>    host/z4.acme.com at RESERVED:KDC-REFERRAL:
>
> A better UI would be nice, yes.  Specifically, it'd be nice to show the
> input service principal name, the method used for canonicalizing it, and
> the canonicalized name.

Do you really want to bump the fcache format version again?
Is making 'klist' provide details that most people will never use worth the 
compatibility issues that would result from such a version bump?



More information about the krbdev mailing list