Date: Tue, 24 Jul 2012 04:13:38 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: Current -fixes GPU formats vs TS 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 >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. 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. magnum On 2012-07-24 03:38, magnum wrote: > That script does not work well. For example, it considers this a > password from mscash_tst.in: > > "characters__17:mscash (user name required for salt in john's format):" > > where the actual password is just "characters__17". > > I think this is better for most files: > grep -v '^#!comment:' $1 | cut -d: -f5 | perl -ne 'use bytes; chomp; > print length, "\n"' | sort -n | uniq -c | sort -nk2 > > I think I'll update the script and add a sum column too. > > magnum > > > On 2012-07-23 23:12, jfoug wrote: >> There is a script in the TS that can 'help'. It is called pw_len_finder.sh >> >> Run it on the input file for the format in question, then add up all lines to the max password allowed. That is the value that needs to be place into the TS data file for that format. >> >> NOTE, multi byte encoding (utf8) will cause that silly little script to not work right. Also note, there may be 1 more 'zero' or negative lengths, than there should be. I need to fix the script to ignore the first line, if it is a comment, and does not contain the required field. >> >> Jim. >> >>> From: magnum [mailto:john.magnum@...hmail.com] >>> >>> These actually look like the formats had their max lengths increased, so >>> maybe we should just adjust the Test Suite? If so, please give me or Jim >>> a notice. I really do not have time to chase information from the source >>> code.
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.