Global Directory signatures

[Greg Sabino Mullane]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
 
I've been working on this problem for a while, and finally had a
chance during this past break to hash out some final issues. I'm
going to be expanding biglumber soon into a "real" keyserver.
However, it's going to be a little different from other keyservers.
The main difference is that the owner of a key will have complete
control of their public key. This means that (for example)
- --recv-key will work, but --send-keys may* not. If you want to make
a change to your public key, you must authenticate (currently via
web/email, but either alone someday). In addition, the keyserver will
only have entries from people who are either in the strong set or who
have added their key to biglumber directly. I consider the fact that
anyone can upload another person's changed public key to a keyserver
a potential Denial of Service, and thus will not allow it.
 
* Keys in the strong set will be allowed to be updated "anonymously"
until such time as the owner logs in to biglumber, at which point it
switches over to a "owner update only" key.
 
- --
Greg Sabino Mullane greg at turnstep.com
PGP Key: 0x14964AC8 200412310202
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
 
-----BEGIN PGP SIGNATURE-----
 
iD8DBQFB1P2tvJuQZxSWSsgRAknZAJ9kIUSHJGaj2fOv/4k4LyV13zwzmgCfdDsv
PNd5HxgPpJqtyAJ3eJ9uQDw=
=y6D6
-----END PGP SIGNATURE-----