[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20051121082919.GB7310@openwall.com>
Date: Mon, 21 Nov 2005 11:29:19 +0300
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: How to use kerberos 5 patch
Hi Frederic,
On Sun, Nov 20, 2005 at 11:35:49AM +0100, Frederic Tronel wrote:
> Benchmarking: Kerberos v5 TGT [krb5 3DES (des3-cbc-sha1)]... DONE
> Raw: 14145 c/s real, 16217 c/s virtual
Great.
> I have taken an example ticket from the patch source code:
>
> $ cat ticket
> $krb5$oskov$ACM.UIUC.EDU$4730d7249765615d6f3652321c4fb
> 76d09fb9cd06faeb0c31b8737f9fdfcde4bd4259c31cb1dff25df39173
> ......
> 2c2265a4ffc72e9fb811da17c7f2887ccb17e2f87cd1f6c28a9afc0c08
> 3a9356a9ee2a28d2e4a01fc7ea90cc8836b8e25650c3a1409b811d0
> bad42a59aa418143291d42d7b1e6cb5b1876a4cc758d721323a762
> e943f774630385c9faa68df6f3a94422f97
There are two problems here:
1. John expects the file to have a format similar to that of /etc/passwd.
At least two colon-separated fields are required: a username and a
password hash. So you need to introduce "usernames" or any identifiers
in their place.
2. The example TGT encodings given in the patch are almost 500
characters long each. When you put them into a file for John to use,
you need to include exactly one TGT encoding per line. You must not
wrap the long encodings.
> $ /usr/local/bin/john ticket
FWIW, when you're installing John system-wide like that, you might want
to define JOHN_SYSTEMWIDE to 1 in params.h, -- or simply not install
John system-wide (this is a feature primarily for use by John packages
in Linux and *BSD distributions).
--
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598 fp: 6429 0D7E F130 C13E C929 6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments
Was I helpful? Please give your feedback here: http://rate.affero.net/solar
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.
