
Date: Sat, 30 Jul 2011 20:00:30 +0400 From: Solar Designer <solar@...nwall.com> To: johnusers@...ts.openwall.com Subject: Re: Sha256 On Sat, Jul 30, 2011 at 05:03:22PM +0200, groszek wrote: > Can you please explain on what ALGORITHM_NAME means then? I assumed it's > the length of hex representation of ciphertext. But didn't pay too much > attention to that, as it had no visible effect on cracking. In ALGORITHM_NAME, I included the number of CPU word bits that the particular implementation (algorithm) of the hashing method makes efficient use of, out of the total word size. For example, "32/64" means that the algorithm (such as a straightforward implementation of MD5) makes use of only 32 bits out of 64 (on a 64bit machine), whereas "128/128 BS SSE2" (such as for a bitslice implementation of DES on SSE2) means that the algorithm makes use of 128 out of 128 bits (in SIMD vectors in this case). ;) I started using this notation prior to inclusion of bitslice DES in JtR, so you could see things such as 24/32 and 48/64 for nonbitslice DES implementations (you still do for Kerberos AFS, which I did not care to move to the bitslice code). Alexander
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.