Re: [Sks-devel] Re: Broken reconciliation

[Daniel Johnson]

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

On 11 Apr 2004 at 0:19, Yaron M. Minsky wrote:
 <snip>
> There are two possible solutions:
> 
> 1) rely on the database cleaner ("sks cleandb").  
 <snip>
> 2) Make the SKS key parsing rules more lenient, allowing V3 keys to
have
> subkeys, like V4 keys.
> 
> Any thoughts on which of these options is preferable?

FWIW, I favor #1.  If this key format violates the specs, we should
not allow it on the network, let alone tolerate existing cases. 
There's no telling what problems may arise later if we let "odd" keys
stay.

- -- 
Through the modem, off the server, over the T1, past the frame-relay,
< < NOTHIN' BUT NET > >
 
Daniel Johnson
address@hidden
http://dannyj.come.to/
Public PGP Keys & other info: http://dannyj.come.to/pgp/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32) - GPGshell v2.95

iD8DBQFAeNQf6vGcUBY+ge8RAiw0AKDFwd5kOh68QACbAyWcC5irH88vkACfT/E8
/nHnrGc26i5KrFGMiF7N0iI=
=EnoT
-----END PGP SIGNATURE-----