[36502] in Kerberos
Re: Kerberos5 ticket to ascii converter?
daemon@ATHENA.MIT.EDU (Wendy Lin)
Tue Sep 30 12:17:46 2014
MIME-Version: 1.0
In-Reply-To: <CAN05THSm4ujoMD1QThF_4P64MgG8NpvBfkS6R1PQsx1wAKSv+Q@mail.gmail.com>
Date: Tue, 30 Sep 2014 18:17:22 +0200
Message-ID: <CA+j=ERqbtG4Zf-nv_TFhRh_Wuvgod3SHNHM84+kAoDPV=NOmCg@mail.gmail.com>
From: Wendy Lin <wendlin1974@gmail.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
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 17:55, ronnie sahlberg <ronniesahlberg@gmail.com> wrote:
> On Tue, Sep 30, 2014 at 8:25 AM, Wendy Lin <wendlin1974@gmail.com> wrote:
>> 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?
>
> One reason is because most of the ticket are encrypted blobs. Without
> decryption these blobs will just look like huge piles of random bytes,
> so there is not really much interesting to see in the ticket.
> If you want to look at the interesting parts of a ticket you really
> want to decrypt these blobs.
OK
is there a C function in libkrb5 which takes a keytab and the data
blob as parameter, and returns the decrypted data blob?
Wendy
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
