Since SHA224 is part of the NIST standard, and TIGER isn't - I question this decision and hope that GPG-2 team will reconsider.
Thank you! -- Regards, Uri Blumenthal <Disclaimer> -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter S. May Sent: Friday, April 27, 2007 11:20 AM To: gnupg-users@gnupg.org Subject: Re: Algorithm 11 not available Charly Avital wrote: > It *would seem* that it is gpg2 (not gpg) that does not support SHA224. Confirmed. 1.4.7 and 2.0.3 (both from source) are also on my system. $ (gpg --version; gpg2 --version) | grep 'Hash:' Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Hash: MD5, SHA1, RIPEMD160, TIGER192, SHA256, SHA384, SHA512 In other words: 1.4.7 supports SHA224 but not TIGER192. 2.0.3 supports TIGER192 but not SHA224. I myself was curious why SHA224 was inexplicably dropped. Not that I assume many people use it, but it seems a bit arbitrary. Is there an explanation, wk? M2C PSM *********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *********************************************************************** _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
