On Tue, 8 Jun 2004 20:51:58 +0300 (EEST), Nikodemus Siivola tsiivola@cc.hut.fi wrote:
You're receiving this email because your common-lisp.net home directory contains no pubkey.asc, but does hold .ssh/authorized_keys.
Please verify that you have access, and put you GPG public key in your home directory as pubkey.asc. You can get GPG to export it with the command "gpg --armor --export <name>".
Just did that. What is this for?
Cheers, Edi.
On Tue, 8 Jun 2004, Edi Weitz wrote:
Please verify that you have access, and put you GPG public key in your home directory as pubkey.asc. You can get GPG to export it with the command "gpg --armor --export <name>".
Just did that. What is this for?
Thank you. I should have explained this in the initial mail, of course.
We treat developer GPG public keys as an opaque identities: if we need to confirm that the person we're dealing with tomorrow is the same one that originally got the account, or eg. in order to send out a new passwords encrypted.
Cheers,
-- Nikodemus "Not as clumsy or random as a C++ or Java. An elegant weapon for a more civilized time."
On Tue, 8 Jun 2004 23:24:15 +0300 (EEST), Nikodemus Siivola tsiivola@cc.hut.fi wrote:
Thank you. I should have explained this in the initial mail, of course.
We treat developer GPG public keys as an opaque identities: if we need to confirm that the person we're dealing with tomorrow is the same one that originally got the account, or eg. in order to send out a new passwords encrypted.
Ah, OK, thanks.
-
Edi Weitz -
Nikodemus Siivola