[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <01f501cd6949$24d60fb0$6e822f10$@net>
Date: Mon, 23 Jul 2012 22:05:13 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: Current -fixes GPU formats vs TS
>From: magnum [mailto:john.magnum@...hmail.com]
>
>Output from new version:
>
>$ ./pw_len_finder.sh mscash_tst.in
>num len sum
>1 0 1
>3 1 4
>16 4 20
>16 5 36
>14 6 50
>41 7 91
>97 8 188
>200 9 388
>218 10 606
>212 11 818
>232 12 1050
>181 13 1231
>120 14 1351
>79 15 1430
>38 16 1468
>8 17 1476
>2 21 1478
>14 24 1492
>8 25 1500
Nice output.
>>From using this tool and looking at --list=format-details I see this:
>
>mscash-cuda should find 1500, finds 1216.
>mscash2-cuda should find 1500, finds 1050.
1050 may be from length of salt (user name). 1050 is seen on other formats, I thought. Or was it due to 'broken' utf8.
>All three raw-sha2-cuda formats should find 1476, and do. Same goes for
>raw-sha512-opencl and xsha512-opencl. I will fix TS and these five are
>set.
>
>pwsafe-cuda should find 1500, finds none.
>md5crypt-opencl should find 1500, finds none.
>phpass-opencl should find 1470, finds none.
>nt-opencl should find 1478, finds none.
>
>Some of the last four had wrong figures in TS too, I will fix that.
There are other things than just pw length to take into account. But the tool 'is' a help.
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.
