[Enigmail] about creating a secure encryption

Ayush Sharma ayush.cena at gmail.com
Tue Jul 1 13:10:32 PDT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Robert,

> DSA-2048 actually calls for SHA224, not SHA256.  I suppose you could use
> SHA256, but you'd lose 32 bits for no reason whatsoever.
I was kinda confused by this comment of yours (as i used to think that
the length of the key used for signing; and the hash algorithm being
used are two factors that are variable and depend on choice, and so then
decide to look it up on the net.)
I found out this link *proving your statement.*
http://lists.gnupg.org/pipermail/gnupg-devel/2006-September/023166.html

What I couldn't still figure out was, that who came out with these
Standards of inter-dependancy between the key length and Hash length
(and thus the Hash Algorithm being used). As the Key length and Hash
functions are two separate things (Ok, not separate in the true sense,
but are inter-dependent *only for HMAC's*).
Don't get me wrong. I totally get the concept behind the relation (and
the practicality of it), but just curious about who came up with this.
Thank you and Warm Regards,
- -Ayush
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: For keyID and its URL see OpenPGP message header

iEYEARECAAYFAkhqjzgACgkQX85fnujYCQYIIQCff/V462wwJS86d/epb/uxC2Ch
GTkAn1f3ztuTCheNTlB+7N4NLSIqx9lW
=JaiP
-----END PGP SIGNATURE-----


More information about the Enigmail mailing list