On Tue, Jul 14, 2009 at 2:13 PM, Pablo Manalastas<[email protected]> wrote: > > My GPG 1.4.9 supports the following algorithms: > > Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA > Cipher: 3DES (S2), CAST5 (S3), BLOWFISH (S4), AES (S7), AES192 (S8), > AES256 (S9), TWOFISH (S10) > Hash: MD5 (H1), SHA1 (H2), RIPEMD160 (H3), SHA256 (H8), SHA384 (H9), > SHA512 (H10), SHA224 (H11) > Compression: Uncompressed (Z0), ZIP (Z1), ZLIB (Z2), BZIP2 (Z3) > > So GPG uses AES256 only for encryption/decryption, and not for computing > hashes. I think SHA256 should work just fine. >
to add this further.. any hash message digest to be use either prone to collision or not is doesnt matter... the most important thing for digital signature is the private key who signs the data must be protected from others to steal or copy it... that is why we need to protect this private key with a passphrase... private key is one of the most important thing for the success of this automated election... fooler. _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
