Date: Thu, 2 Feb 2012 16:48:53 +0000 From: Alex Sicamiotis <alekshs@...mail.com> To: <john-users@...ts.openwall.com> Subject: RE: DES with OpenMP > > BTW, you could similarly experiment with MD5_std_cpt (MD5_std.h) and > > BF_cpt (BF_std.h). These should make a lot less of a difference (and > > for their respective hash types only), though. > > Ok, just did this (GCC 4.6.2) with 2 threads on the 1.7.9 (no-jumbo). BF default value is 3. I used 1-2-3-4-5-6-8-16-32 for bf_cpt. Performance was the same throughout 2180 c/s for 1, 2180 c/s for 3, 2180 c/s for 32. So no gains in BF. Apparently it is too slow to crack to be affected from this. MD5 default value was 128. I used 1-4-8-16-32-64-128-256-512. Performance for 1,4,8,16,32 and 64 was ranging between 34.520 to 34.530 c/s. Performance for 128 (def) was 34.456 (0.2% degradation compared to 64-32-16-8-4-1). Performance for 256 was 34.365, more degradation. Performance for 512 was 34.331, more degradation. In general not much to improve here unlike DES and LM, but still if anyone wants to find 0.2% with core2 hardware they might try lowering the value to 64.
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.