[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABob6ipjh3_0DOBk=1RZ_dFHYeN31rT7NqHODBpgiGFG5r1adA@mail.gmail.com>
Date: Thu, 3 Jan 2013 04:52:16 +0100
From: Lukas Odzioba <lukas.odzioba@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Multiple formats accepting the same raw hashes
2013/1/2 Brad Tilley <rbt@....us>:
> 1. Silently use the first hash format that matches - incorrect
> 2. Use the first match, and also mention all the other formats that match - incorrect
> 3. When there are multiple matching formats, JtR should stop and ask the user to specify one - correct
I agree with 3rd, even if user is aware what he is doing, making
stupid mistake is harder.
> Now, should the end-user opt for --format=raw_md5 and the hashes are 160 bits, then we have the issue of the user being wrong, not JtR being wrong because it assumed that the hash was X when in fact it was Y. Programs should be wrong less often than users. If the program does not know exactly what the input is, don't guess or pick the first match and be wrong, stop and ask the user. If the user selects the wrong format (160 bit MD5 hashes) then JtR should stop and explain that MD5 hashes have 128 bits, the hashes specified have 160, please try another format.
"You tried to crack hash which have Y bits, but you specified format X
which have Y bits".
This would be confusing.
Lukas
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.
