Commit Level (Level 3 → Level 1) for Jan Keromnes

RESOLVED FIXED

Status

Infrastructure & Operations
MOC: Service Requests
RESOLVED FIXED
9 months ago
9 months ago

People

(Reporter: janx, Assigned: Usul)

Tracking

Details

Attachments

(2 attachments)

(Reporter)

Description

9 months ago
Hi Marcia,

I currently have scm_level_3 (bug 1053058), but I would like to volunteer for a "downgrade" back to scm_level_1.

I mainly use try, checkin-needed and autoland, so I don't need direct push access to all repositories, and I very much agree with the need to reduce the number of highly privileged credentials out there.

Additionally, I would like my previous SSH key to be revoked (I retired it, but did not lose it), and I will shortly upload 2 new keys that I intend to use with scm_level_1, if possible.

Thanks!
(Reporter)

Comment 1

9 months ago
Created attachment 8868769 [details]
new_key1.pub
(Reporter)

Comment 2

9 months ago
Created attachment 8868770 [details]
new_key2.pub
(Reporter)

Comment 3

9 months ago
(Regarding the old SSH key to retire, please revoke the one from bug 965810).

Comment 4

9 months ago
You should be able to perform the SSH key modifications via login.mozilla.com.

Updated

9 months ago
Assignee: mozillamarcia.knous → nobody
Component: Repository Account Requests → MOC: Service Requests
Product: mozilla.org → Infrastructure & Operations
QA Contact: lypulong

Updated

9 months ago
Assignee: nobody → ludovic
Status: NEW → ASSIGNED
(Assignee)

Comment 5

9 months ago
removed level2 and level3 - there was only one key; I didn't touch keys.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → FIXED
(Reporter)

Comment 6

9 months ago
Note for posterity: Thanks to Usul's help I was able to revoke my old key, and upload the 2 new keys, using my "@linux.com" LDAP account on login.mozilla.com.

I've inadvertently uploaded my 2 new keys on my "@mozilla.com" LDAP account as well, but I guess that's OK (I'll just have to delete them from both accounts when I decide to revoke them).
You need to log in before you can comment on or make changes to this bug.