Opened 6 months ago

Last modified 8 weeks ago

#27895 reopened task

Add push access to alexishan

Reported by: legind Owned by: tor-gitadm
Priority: Medium Milestone:
Component: Internal Services/Service - git Version:
Severity: Normal Keywords:
Cc: alexishan Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Hash: SHA256

Please give push access for to alexishan.  She will be maintaining HTTPS Everywhere.  Here is her ssh pubkey:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDGyeWxDaS3c9lQ1WH991fMk61uAiLyHtb+azVCdXjxQ97mrLYCmKLmqrPvbFdL9bzpYHkuWhbmJywn/PWYxqjkqbUJAQJPtaGPpO5KDkwSTbOyCQ4c7J1ztp0eWZJMkNMg9kZeTdUgdPjoVfsGzbkBJ6CzIepZlt+TzIajUy6yvtAWyEzrkdn369wLJidyiOqhvk4EjaUTN0aRO8SaW6RcVkV9/zkj+jr+JeP+vk0L1iKuXogvCFjFhuhfNENTFt5+Le/Sjq061QZs4xoqrB7a0ay4++FwWyGf9sd4yQe/1c2fMMGyaKLKbGS0nNB3v5tuehc3hhVrKppQUfH37tf4HSwGIs+9hXSI4IBAMRtiSz9owEYS/9EARMTMcvuNUQfgXDdtXWLldHvcTd0h3UQKnuIi1gC1lxww+9pqYIodX2NrZHfLhahtTx4CW/3knidmeVIAphezWCUlaIkgtngfgLbEBwe1Wg2C5d4n2IPhJv3XpL99HvteT05dixOLix75Qtm0imhokwnLpnO24hKnWSh+WpPh8wuyIuiBL/xlb+d17y2oH+Bbd9YQjZxpsugJsVatcl797smkrZN5UfejSzUbZ3+dcBAyhs3L2gBE/hNEaYnVbAlpU8FAXD91w05pRWn5YnC/yvo5Zzu3IGGI9/Ha3nzUt8KDgSFSFQW/dQ==

I'm unsure who to address this to, so assigning to teor for triage (thanks teor!)



Child Tickets

Attachments (1)

pub.txt (740 bytes) - added by alexishan 2 months ago.

Download all attachments as: .zip

Change History (16)

comment:1 Changed 6 months ago by teor

Component: - Select a componentInternal Services/Service - git
Owner: teor deleted

I can't modify git, but one of the git admins should do this task soon.

comment:2 Changed 5 months ago by teor

Owner: set to qbi

Assigning the task to me meant that it didn't get assigned to the default git admin.

comment:3 Changed 5 months ago by qbi

Owner: changed from qbi to tor-gitadm

The correct group of people is tor-gitadm. AFAIR nickm is one of the git maintainers. I reassigned the ticket to tor-gitadm.

comment:4 Changed 5 months ago by irl

Thanks to Hans for providing a GPG trust link between me and Bill. (:

In theory this is a valid request and I would process it, but to complete this, we'll need to create a new LDAP account for alexishan first.

legind: Please follow the steps detailed at and indicate in this ticket when the account has been created.

comment:5 Changed 5 months ago by irl

Status: assignedneeds_information

comment:6 Changed 5 months ago by legind

Ref: #28112

comment:7 Changed 5 months ago by legind

irl: The account has been created, see #28112.

comment:8 Changed 5 months ago by irl

@https-everywhere = mikeperry pde schoen dtauerbach micah yan jsha legind alexishan

Please let me know if this list should be shortened (in a new ticket).

Is there a need for a user/alexishan/https-everywhere.git for pushing branches for review? I see lots of other people in the above list have that repository in their user namespace.

If so then I can create that, if not please mark this ticket as fixed.

comment:9 Changed 5 months ago by legind

irl: I don't think that's necessary, I think that's part of an antiquated process. Thanks!

comment:10 Changed 5 months ago by legind

Resolution: fixed
Status: needs_informationclosed

Changed 2 months ago by alexishan

Attachment: pub.txt added


comment:11 Changed 2 months ago by alexishan

Reopening this issue since it seems I still can't ssh into git@…. My public key gets denied. In case it was malformed I am reattaching via a plain text file.

comment:12 Changed 2 months ago by alexishan

Resolution: fixed
Status: closedreopened

comment:13 Changed 2 months ago by irl

Updating your SSH key is a self-service task.

Please ask on #tor-project on if you have problems using this service, and someone there will be able to help you.

comment:14 Changed 2 months ago by irl

Alexis Hancock (uid=alexishan,ou=users,dc=torproject,dc=org)

The user definitely exists in LDAP so it should just be a key issue.

comment:15 Changed 8 weeks ago by alexishan

I'm trying to use the email self-service, but I normally get this error back about a "malformed" email


Your request to the mail gateway is malformed, or an internal processing
error occured. The information below may help you, or the gateway
administrator to identify the problem.

Error: Unable to check the signature or the signature was invalid:
==> <class 'userdir_exceptions.UDFormatError'>: UDFormatError: Verification of signature failed

Will email the admin support to try and clarify why this is happening

Note: See TracTickets for help on using tickets.