In
<D8BD79FBE274D211B7E500A0C9AAD4D7594B5F(_at_)mail(_dot_)mia(_dot_)co(_dot_)uk>,
on 03/08/99
at 11:48 AM, "Simpson, Sam" <s(_dot_)simpson(_at_)mia(_dot_)co(_dot_)uk>
said:
I don't want to "throw a Sternlight" on this point - but frankly I am
concerned.
Well IMHO we have enough good symetric cyphers in there right now:
9.2. Symmetric Key Algorithms
ID Algorithm
-- ---------
0 - Plaintext or unencrypted data
1 - IDEA [IDEA]
2 - Triple-DES (DES-EDE, as per spec -
168 bit key derived from 192)
3 - CAST5 (128 bit key, as per RFC 2144)
4 - Blowfish (128 bit key, 16 rounds) [BLOWFISH]
5 - SAFER-SK128 (13 rounds) [SAFER]
6 - Reserved for DES/SK
7 - Reserved for AES with 128-bit key
8 - Reserved for AES with 192-bit key
9 - Reserved for AES with 256-bit key
100 to 110 - Private/Experimental algorithm.
Implementations MUST implement Triple-DES. Implementations SHOULD
implement IDEA and CAST5.Implementations MAY implement any other
algorithm.
But then again everyone has their pet algorithm that they want to put into
the code. Code ranges from 100 to 110 are reserved for
private/experimental algorithms and that is where twofish and the rest
should go. Unfortunately if NAI decides to start using ID #10 for twofish
there is very little the rest of us can do about it (as seen with the
PhotoID). I have asked several times for us to establish a formal
mechanism for assigning ID numbers, as it stands now it is first come
first serve.
--
---------------------------------------------------------------
William H. Geiger III http://www.openpgp.net
Geiger Consulting Cooking With Warp 4.0
Author of E-Secure - PGP Front End for MR/2 Ice
PGP & MR/2 the only way for secure e-mail.
OS/2 PGP 5.0 at: http://www.openpgp.net/pgp.html
Talk About PGP on IRC EFNet Channel: #pgp Nick: whgiii
---------------------------------------------------------------