-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jon Callas wrote:
At 3:49 PM +0200 4/11/01, disastry(_at_)saiknes(_dot_)lv wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
isn't it time to define new algorithm numbers for SHA2 ?
8 for SHA256 (and maybe 9,10 for SHA384,512?)
the bigger problem however is with OIDs...
none of SHA2 have OIDs defined, just like HAVAL and TIGER :(
That is, in fact, the bigger problem. We can either finesse it -- we agree
on an OID to use for them -- or we wait for some other OID space to assign
them.
there is OIDs for SHA256, SHA384, SHA512 !
The ASN.1 OIDs are:
- SHA256: 2.16.840.1.101.3.4.2.1
- SHA384: 2.16.840.1.101.3.4.2.2
- SHA512: 2.16.840.1.101.3.4.2.3
The hexadecimal representations are:
- SHA256: 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x01
- SHA384: 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x02
- SHA512: 0x60, 0x86, 0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x03
so
The full hash prefixes for these are:
SHA256: 0x30, 0x31, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x01, 0x05,
0x00, 0x04, 0x20
SHA384: 0x30, 0x41, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x02, 0x05,
0x00, 0x04, 0x30
SHA512: 0x30, 0x51, 0x30, 0x0d, 0x06, 0x09, 0x60, 0x86,
0x48, 0x01, 0x65, 0x03, 0x04, 0x02, 0x03, 0x05,
0x00, 0x04, 0x40
so how about assigning algorithm numbers for SHA2:
ID Algorithm Text Name
-- --------- ---- ----
8 - SHA256 "SHA256"
9 - SHA384 "SHA384"
10 - SHA512 "SHA512"
?
== <EOF> ==
Disastry http://i.am/disastry/
http://disastry.dhs.org/pgp <----PGP plugins for Netscape and MDaemon
^--GPG for Win32 (supports loadable modules and IDEA)
^---PGP 2.6.3ia-multi03 (supports IDEA, CAST5, BLOWFISH, TWOFISH,
AES, 3DES ciphers and MD5, SHA1, RIPEMD160 hashes)
-----BEGIN PGP SIGNATURE-----
Version: Netscape PGP half-Plugin 0.15 by Disastry / PGPsdk v1.7.1
iQA/AwUBOt6QwzBaTVEuJQxkEQI+WACgz9uOr++iIuUD8HN2coNGv5XGgNsAn29A
WGhf3roDQImhNiMX5W11za4H
=wvub
-----END PGP SIGNATURE-----