Bug 25208 - Update GPG key
Summary: Update GPG key
Status: RESOLVED FIXED
Alias: None
Product: freedesktop.org
Classification: Unclassified
Component: Account Modification Requests (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: fd.o Admin Massive
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-20 17:25 UTC by Dana Jansens
Modified: 2010-02-21 13:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
gpg key (2.17 KB, text/plain)
2009-11-20 17:25 UTC, Dana Jansens
Details

Description Dana Jansens 2009-11-20 17:25:44 UTC
Created attachment 31359 [details]
gpg key

Hello sitewranglers,

Would you please update the GPG key on my account to the one attached.  Thanks.
Comment 1 Tollef Fog Heen 2010-02-09 11:27:48 UTC
Hi,

to replace your key, we would like some kind of proof that you are who you are, some suggestions are:

* Get your key signed by someone else at fd.o
* Indicate which groups you have access to on fd.o
* Indicate 3 files in your home directory
* Anything else which verifies who you are

Could you provide us with any of this, by any chance?
Comment 2 Dana Jansens 2010-02-09 12:17:16 UTC
How about here: http://cg.scs.carleton.ca/~dana/ and scroll down to the bottom, I list my PGP key fingerprint there.  You can also try my email account if you wish to verify I own it.

I don't know any of the fd.o people personally, and I haven't used my account in a few years (as the key was expired), making the second two difficult.
Comment 3 Tollef Fog Heen 2010-02-21 13:21:07 UTC
I've checked a bit and your request seems legitimate, so I have updated the key in the keyring.  You should now be able to update any SSH keys and log in again. In the future, remember that you can just update the expiry date of a key; I'm quite happy to refresh keys that are already in the keyring, but replacing keys needs a bit more checking.

Sorry for the delay in tending to your request.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.