Re: [clo-devel] Re: Please upload your public GPG key to common-lisp.net

Mario Mommer <mommer@igpm.rwth-aachen.de> writes:
Some redundancy would certainly be good. In case something bad happens we would have to hack your box to run the site, btw.
Good point. I will tell you and Nikodemus the root password plus the passphrase for the common-lisp.net private key (once I've created it). Should we also perhaps distribute a key-revocation certificate for the common-lisp.net key just in case it gets out in the wild? Erik.

Erik Enge <eenge@prium.net> writes:
Mario Mommer <mommer@igpm.rwth-aachen.de> writes:
Some redundancy would certainly be good. In case something bad happens we would have to hack your box to run the site, btw.
Good point. I will tell you and Nikodemus the root password plus the passphrase for the common-lisp.net private key (once I've created it).
Should we also perhaps distribute a key-revocation certificate for the common-lisp.net key just in case it gets out in the wild?
Yes, I think we should do all this. Unforseen situations are exactly that: unforseen. Any one of us should be able to react if something goes wrong and he does not find any of the other two. In limits, of course. Regards, Mario.
participants (2)
-
Erik Enge
-
Mario Mommer