[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP1954F92A17675F5DDCA8747FD3A0@phx.gbl>
Date: Thu, 12 Apr 2012 11:28:29 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: MSCash2 formats reliability & usability
On 04/12/2012 12:17 AM, Solar Designer wrote:
> Jim, magnum, Lukas, Sayantan -
>
> We have three JtR formats for MSCash2: CPU, CUDA, OpenCL.
>
> The CPU one supports many different representations of MSCash2 hashes
> and has many test vectors of different form ($DCC2$ prefix present vs.
> not, iteration count included vs. not, username included vs. separate).
> This is great, although the format's support for variable iteration
> counts is probably unneeded (there are no non-10240 MSCash2 hashes in
> the wild, as far as I'm aware).
What about the other alternative:
Just always add the iteration count, even if it is the default of 10240?
This would also prevent wrong detection as hmac-md5.
Generally, I would prefer to have at least one representation per
supported format which is not considered valid by any other format, at
least not by any other format which is tested earlier.
Ideally, this format representation should not only be used for new
john.pot lines, there should also be an easy way to convert john.pot so
that all lines use the preferred format representation.
Even better would be a way to convert the input files as well, so that
the hashes to be cracked are converted into the preferred format
representation.
Frank
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.
