[36576] in Kerberos
Re: Help interpreting wireshark traces
daemon@ATHENA.MIT.EDU (Rick van Rein)
Sat Oct 25 18:36:43 2014
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Rick van Rein <rick@openfortress.nl>
In-Reply-To: <544BF88C.2040405@lhanke.de>
Date: Sun, 26 Oct 2014 00:36:26 +0200
Message-Id: <3A85C0A2-8ADB-463D-AC59-EAE3E746583D@openfortress.nl>
To: debian@lhanke.de
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="windows-1252"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit
Hi Lars,
Disclaiming any experience with AD; but this sounds like the domain join
might have replaced the keytab that held the old service ticket, or perhaps
it is now unreachable because AD has renamed the realm.
SASL traces should be visible, at least if you’re not running inside TLS, which
is not necessary for GSS-API (but it is for data privacy since SASL apps usually
don’t use the C_Wrap() facilities).
I hope this helps!
-Rick
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
