[9993] in Kerberos-V5-bugs
Re: [krbdev.mit.edu #194] a stash file is not a keytab
daemon@ATHENA.MIT.EDU (Tom Yu via RT)
Thu Jul 3 11:40:54 2008
Date: Tue, 1 Jul 2008 19:17:46 -0400 (EDT)
In-Reply-To: <rt-194@krbdev.mit.edu>
Message-ID: <rt-194-27269.10.6754371902387@krbdev.mit.edu>
Mail-Followup-To: rt@krbdev.mit.edu
To: (watchers of [krbdev.mit.edu #194])
Mail-Copies-To: never
From: "Tom Yu via RT" <rt-comment@krbdev.MIT.EDU>
Reply-To: rt-comment@krbdev.MIT.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
"Alexandra Ellwood via RT" <rt-comment@krbdev.mit.edu> writes:
> [tlyu - Tue Jul 1 16:31:32 2008]:
>
>>
>> I think we can treat ticket #5662 as the stash file byte order
>> independence issue. As far as I know, keytabs are a single byte
>> order.
>
> Keytabs aren't byte order independent? So if a sysadmin creates a
> keytab for me on a machine with a different endianness from mine do
> I have to do something to it for it to work?
I meant that as far as I know, keytabs are a single
(platform-independent) byte order, and a brief scan of the source code
agrees.
> Also this bug seems to be specifically about wanting a stash file to
> be a keytab. Machine independence is listed as just one of the side
> benefits of doing this.
Agreed.
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
