[27414] in Kerberos
Re: Windows Integration attempt #2
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Feb 8 12:54:27 2007
From: Sam Hartman <hartmans@mit.edu>
To: Quanah Gibson-Mount <quanah@stanford.edu>
Date: Thu, 08 Feb 2007 12:54:01 -0500
In-Reply-To: <762A699A70136C6F4BCF4C64@SW-90-717-287-3.stanford.edu> (Quanah
Gibson-Mount's message of "Thu, 08 Feb 2007 09:50:57 -0800")
Message-ID: <tslsldga62u.fsf@cz.mit.edu>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
>>>>> "Quanah" == Quanah Gibson-Mount <quanah@stanford.edu> writes:
Quanah> --On Thursday, February 08, 2007 7:32 AM -0500 Sam Hartman
Quanah> <hartmans@mit.edu> wrote:
>>>>>>> "Quanah" == Quanah Gibson-Mount <quanah@stanford.edu>
>>>>>>> writes:
>>
Quanah> --On Wednesday, February 07, 2007 5:07 PM -0500 Sam
Quanah> Hartman
Quanah> <hartmans@mit.edu> wrote:
>> >> I would be suspicious of whether you had properly managed
>> to >> set your machine password.
>>
Quanah> Define "machine password". You mean the password used
Quanah> between the machine and the KDC for the keytab that was
Quanah> created? That bit is obviously working because when those
Quanah> don't match, the KDC logs an error, which it isn't doing.
Quanah> In any case, I had that particular password in my C&P
Quanah> buffer, and simple pasted it in for both the KDC and the
Quanah> windows box, so it would be particularly difficult for it
Quanah> to be a typo...
>> If the salt types are inconsistent or something I could see
>> the key working to obtain tickets but not to decrypt them.
Quanah> Hm, interesting. Is there an easy way to diagnose that?
Not really.
--Sam
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
