[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 20 Sep 2015 07:05:06 -0700
From: Fred Wang <waffle.contest@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Judy array
On Sep 20, 2015, at 12:28 AM, Solar Designer <solar@...nwall.com> wrote:
> Can you give the current JtR (in magnum's repo on GitHub) a try?
> We need to figure out the number of cracks discrepancy. I am getting
> 1709703 in all of these tests, so I don't know why you only got
> 1481414. (We'll also need to figure out the smaller 1710650 vs. 1709703
> discrepancy later.)
Cloned, and built clean. I still don't see the same answers as you.
./john --format=raw-md5 --wordlist=/big/words/10m.pass --rules=best64 --pot=foo.pot 29m.txt
wc -l foo.pot
1793671
./john --format=raw-md5 --pot=foo.pot --show 29m.txt >29m.res
tail -2 29m.res
1707727 password hashes cracked, 27304531 left
I've put foo.pot and 29m.res in a 7z archive for you:
https://www.sendspace.com/file/qty8vd
>
> Also, why do you only go for up to 32 threads? 2x E5-2680v2 has 40
> hardware threads (10 physical cores per CPU chip). How many are seen in
> /proc/cpuinfo for you? I used 32 threads on our 2x E5-2670v1 because
> these are older v1 chips here.
Because I was using an AWS instance, so I could have a completely idle environment to test in.
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.
