[36499] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Kerberos5 ticket to ascii converter?

daemon@ATHENA.MIT.EDU (Rick van Rein)
Tue Sep 30 09:26:14 2014

Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Rick van Rein <rick@openfortress.nl>
In-Reply-To: <CA+j=ERoouQu-BLRU1o-oBN+p-F_RMEDTqc9n+OQdP+68OXUPyA@mail.gmail.com>
Date: Tue, 30 Sep 2014 15:25:53 +0200
Message-Id: <B27AA961-7E41-4F7E-8E9B-30BB607C6B47@openfortress.nl>
To: Wendy Lin <wendlin1974@gmail.com>
Cc: "<kerberos@mit.edu>" <kerberos@mit.edu>
Content-Type: text/plain; charset="windows-1252"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit

Hi,

>>> Does Kerberos5 have a ticket to ascii converter so someone can see
>>> what a ticket looks like in plain text?
>> 
>> You might use any ASN.1 parser to see the structure, without it actually being spelled out in terms of the Kerberos field names.
> 
> Is the file format of the ticket cache in ASN.1?

That would depend on its implementation.  You asked for tickets ;-) which are defined in ASN.1 in the RFCs.  I think the WireShark suggestion is better than mine, but it won’t do what you are asking.

-Rick
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos


home help back first fref pref prev next nref lref last post