-----BEGIN PGP SIGNED MESSAGE-----
In <slrn6hmtuv(_dot_)k2(_dot_)lutz(_at_)taranis(_dot_)iks-jena(_dot_)de>, on
03/27/98
at 09:56 AM, lutz(_at_)taranis(_dot_)iks-jena(_dot_)de (Lutz Donnerhacke)
said:
* Christopher Creutzig wrote:
On 11 Mar 1998, Lutz Donnerhacke wrote:
-> >think that there are some more pressing issues like the ability to revoke
-> >userID's if modifying the format is still open game.
->
-> No. It's already solved an implemented since about than a year.
I haven't seen it in the spec yet. Your reference implementation does not
define anything, it *only* implements the spec and serves as something
people can check their programs for interoperability with. It had been
solved with the old key format, though...
It is a feature of PGP2.6.3(i)n since months.
Yes but that does not replace the need for it to be outlined in the spec.
- --
- ---------------------------------------------------------------
William H. Geiger III http://users.invweb.net/~whgiii
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 2.6.3a at: http://users.invweb.net/~whgiii/esecure.html
- ---------------------------------------------------------------
Tag-O-Matic: The sad thing about Windows bashing is it's all true.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a-sha1
Charset: cp850
Comment: Registered_User_E-Secure_v1.1b1_ES000000
iQCVAwUBNRwR149Co1n+aLhhAQGhBAQAprbhuSeX6Ce+65fjmTF38BiG1q9+PqOt
BXy4eOB/V9rlqmBD6R/kmGrLk8Q/UAoS4Kw3S4ZemKJowZ83KpcnKOdCJCpaSIqM
KuHYaDRELimwIAFIyGAmt5w7JurCXhLWJaZxnxYWsaMGz9W+vG6F0sqd/61jH/x/
ACpdsuAUF4s=
=vi4E
-----END PGP SIGNATURE-----