Closed Bug 1300281 Opened 8 years ago Closed 8 years ago

re-enable ssh access Josh Aas

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

Product:
Infrastructure & Operations
Component:
MOC: Service Requests
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jaas, Assigned: vinh)

Details

Attachments

(1 file)

Josh's public key
740 bytes, text/plain
Details
Attached file Josh's public key — 
Please enable ssh access for me so I can push with mercurial. I want to use the address jaas@kflag.net. Public key attached.
(In reply to Josh Aas from comment #0)
> Created attachment 8787845 [details]
> Josh's public key
> 
> Please enable ssh access for me so I can push with mercurial. I want to use
> the address jaas@kflag.net. Public key attached.

You don't have access to your old gmail and @moco adresses ? This woulfd be easier for us to -re-enable and verify identity.
Assignee: nobody → vhua
I do but for various reasons I don't want to use them going forward. I can use them to help with verification now if you like, but I want to use jaas@kflag.net going forward.
Josh - Can you provide me the original bug #?
Flags: needinfo?(jaas)
(In reply to Vinh Hua [:vinh] from comment #3)
> Josh - Can you provide me the original bug #?

I don't know what that would be. I don't see any other relevant bug.
Flags: needinfo?(jaas)
account created, temp pw emailed
keys added
hg bit enabled
level 3 commit enabled
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: