C. Scott Ananian wrote:
We make currently make heavy use of hashing in our upgrade
verification infrastructure. I'd like to find the fastest possible
implementation of the SHA-256 and/or RIPEMD-160 algorithms. Can
anyone offer me advice on the proper compilation options and
strategies for
C. Scott Ananian writes:
We make currently make heavy use of hashing in our upgrade
verification infrastructure. I'd like to find the fastest possible
implementation of the SHA-256 and/or RIPEMD-160 algorithms.
If it has to be SHA-256 or RIPEMD-160, I don't think you'll
be finding any
On 9/22/07, Mitch Bradley [EMAIL PROTECTED] wrote:
Some timing for libtomcrypt with various compilation options. All times
are for hashing 1MiB of data from memory, timed under Open Firmware with
interrupts disabled.
[...]
So, with this code, the slow version does sha256 at about 4 MiB/sec,
There is a crypto++ library:
hash functions SHA-1 http://www.cryptolounge.org/wiki/SHA-1, SHA-2
http://www.cryptolounge.org/wiki/FIPS_180-2 (SHA-224, SHA-256,
SHA-384, and SHA-512), Tiger http://www.cryptolounge.org/wiki/Tiger,
WHIRLPOOL http://www.cryptolounge.org/wiki/WHIRLPOOL, RIPEMD-128,
On 9/22/07, Albert Cahalan [EMAIL PROTECTED] wrote:
You don't seem terribly committed to any particular hash.
How about picking one that the Geode is especially good at?
You have AES acceleration hardware, and there are several
ways to turn a block cipher like AES into a hash.
This is
We make currently make heavy use of hashing in our upgrade
verification infrastructure. I'd like to find the fastest possible
implementation of the SHA-256 and/or RIPEMD-160 algorithms. Can
anyone offer me advice on the proper compilation options and
strategies for maximum performance on the
We make currently make heavy use of hashing in our upgrade
verification infrastructure. I'd like to find the fastest possible
implementation of the SHA-256 and/or RIPEMD-160 algorithms. Can
anyone offer me advice on the proper compilation options and
strategies for maximum performance on
