[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Aug 2011 01:30:04 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: Tripcodes, take 2
Hi,
We're busy preparing for KoreLogic's password cracking contest, so I
doubt that people will spend much time commenting on tripcodes now. ;-)
On Tue, Aug 02, 2011 at 06:21:02PM -0700, Corbin Simpson wrote:
> So, as a favor to a friend, I'm committing myself to getting tripcodes
> into JtR.
That's nice. Thanks!
> I was stymied last time by a confusing facet of the format
> system: There's no way to specify that a hash might have multiple
> possible salts. Tripcodes always have 3969 possible salts for any
> given ciphertext, corresponding to a mapping of the second and third
> characters of the plaintext. (Specifically, they are mapped down to 63
> possibilities per character, and 63**2 is 3969.)
>
> However, I noticed that, for DES, there is a "many salts" message
> during benchmarking. I can't help but be curious: Is there a way to
> tell the DES cruncher to try a variety of salts for a given
> ciphertext?
The way you describe the problem (which may or may not be the correct
description), you'd have crypt_all() loop over the 3969 salts. Yes,
you'd have that loop inside of crypt_all(), not exposing it to the rest
of JtR.
However, to get a more reliable answer you need to provide an example.
I am not familiar with tripcodes, and few in here are. So please post
an example input to JtR (with your future patch) and the desired output,
and show how to verify that this is the correct output.
Alexander
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.
