Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 24 Jun 2010 22:43:18 +0400
From: Solar Designer <>
Subject: Re: john the ripper for Kerberos Ticket

Kristian -

On Thu, Jun 24, 2010 at 10:12:40PM +0400, Solar Designer wrote:
> ... I was
> not able to quickly crack "your" password, perhaps because it is not a
> weak one and/or because I did not guess the realm name correctly and/or
> because you did not provide the correct username.

It turns out there was another (sufficient) reason why I would not be
able to crack the password in this way.  The code expects the TGT to be
of exactly 228 bytes - or 456 hex chars.  The string you posted is 552
hex chars - or 276 bytes.  So we have 48 bytes or 96 hex chars extra.
It is not clear to me why this is so (I am not familiar with Kerberos).
Maybe you have something different/unsupported, or maybe the string
simply contains extra data that you need to remove.   I've tried
removing 96 chars from the beginning or from the end:


Maybe one of these is right, but most likely not.  (I was still not able
to crack the password.)  You're in a better position to experiment with
this since you hopefully know the username and the realm name for sure.

I assume you're authorized to be doing this, and I assume that the TGT
you posted was for an obviously-unimportant account or/and the password
has since been changed.

I've attached a revised patch, with the encoding length check added (it
will correctly refuse to load the "atom" line from my previous message).


View attachment "john-1.7.6-jumbo-3-krb5-2.diff" of type "text/plain" (3915 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.