[36500] in Kerberos

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

Re: Kerberos5 ticket to ascii converter?

daemon@ATHENA.MIT.EDU (Wendy Lin)
Tue Sep 30 11:25:58 2014

MIME-Version: 1.0
In-Reply-To: <B27AA961-7E41-4F7E-8E9B-30BB607C6B47@openfortress.nl>
Date: Tue, 30 Sep 2014 17:25:36 +0200
Message-ID: <CA+j=ERoTq5N-XcZnUZ89rgtKtjmkhtrgZa8AZ-ZEpSiqZTvqsQ@mail.gmail.com>
From: Wendy Lin <wendlin1974@gmail.com>
To: Rick van Rein <rick@openfortress.nl>
Cc: "<kerberos@mit.edu>" <kerberos@mit.edu>
Content-Type: text/plain; charset="utf-8"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit

On 30 September 2014 15:25, Rick van Rein <rick@openfortress.nl> wrote:
> 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.

MIT kerberos 1.12, DIR: cache

> 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.

Why?

Wendy

________________________________________________
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