[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Aug 2012 22:08:25 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: mscash2: CPU and GPU formats disagree about canonical hash representation
(and use different test vectors)
I noticed this with the contest edition during CMIYC 2012, but skimming
over the john-1.7.9-jumbo-6-fixes branch, I think the problem exists in
all trees.
The CPU format supports a variable iteration count (default being
10240), and always uses the iteration count as part of the canonical
hash representation, like this:
$DCC2$10240#test1#607bbe89611e37446e736f7856515bf8
OTOH, mscash2-cuda and mscash2-opencl don't include the iteration count
into the canonical hash representation, but IMO they should,even if they
only support a hard coded iteration count of 10240, instead of this:
$DCC2$eighteencharacters#fc5df74eca97afd7cd5abb0032496223
On a related note, I wonder why CPU and GPU implementations seem to use
completely separate test vectors, instead of at least reusing some o the
tests of the format which was implemented first.
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.
