Closed
Bug 1053263
Opened 10 years ago
Closed 10 years ago
Lost private ssh key, new public key for dhardison@mozilla.com
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dylan, Assigned: ashish)
References
Details
Attachments
(1 file)
|
737 bytes,
text/plain
|
Details |
Due to SSD failure, I no longer have access to my old private key. Note: it is not lost in the sense that someone else may have access to it, as it never left the (encrypted) drive of my mozilla laptop, but the old one should still be removed. The new public key is attached.
|
Assignee | |
Updated•10 years ago
|
Assignee: server-ops → ashish
Status: NEW → ASSIGNED
|
|
Assignee | |
Updated•10 years ago
|
Attachment #8472385 -
Attachment mime type: application/vnd.ms-publisher → text/plain
|
|
Assignee | |
Comment 1•10 years ago
|
||
Replaced key in LDAP. It should propagate everywhere within ~45 mins.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
Comment 2•10 years ago
|
||
It may have been better to revoke/invalidate the old key and add the new key, rather than replacing the old. Gitolite, and potentially other systems that get keys from ldap via puppet, doesn't handle replaced keys.. well, at all, apparently.
|
||
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•