Thanks, I'll try the hex-decoding idea to see if that helps, I did consider that, but wasn't sure it would have that much impact. Will look at the static memory allocation as well.
I go parallel over the alphabet, not the hashes. For example, assuming that a person has selected a password from 94 English chars, and I have 94 cores then I could start at 94 different points (iterating forward through each point). So in that scenario (94 CPUs and 94 chars), I use one CPU or core (basically a hardware thread) on each char. CPU1 only does char A, CPU2 only does char B, etc. So parallel hashing on the same HW thread would not occur. With fewer HW threads, each thread would iterate through a subset (3, 4, 5, or upto total chars/2 for a dual core system) of the 94 chars and then stop. That being the approach, I would think any sha1 library would do, and I like Crypto++ due to its wealth of hash functions compared to other libs. I appreciate the tips, Brad -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
