Opened 4 years ago

Closed 4 years ago

Last modified 22 months ago

#18223 closed task (fixed)

Create LDAP account for push access to HTTPS Everywhere

Reported by: legind Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: pde Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hello. I work at EFF and I'm going to be doing releases of HTTPS Everywhere. I need push access to the HTTPSE repo and LDAP access.

My PGP key is available on the public keyservers, fp:

977A 04EC 512A 9D0D B4A5 6E0E CDCA E8ED 6842 C592

It is signed by Peter Eckersley. Please let me know any next steps involved.

Child Tickets

Change History (5)

comment:1 Changed 4 years ago by cypherpunks

Component: generalTor Sysadmin Team
Owner: set to tpa

comment:2 Changed 4 years ago by weasel

Please have Peter (or anybody else with a tpo account) add here a signed request for the account (and its verified information) as per step 1 of https://help.torproject.org/tsa/doc/accounts/

Cheers,

comment:3 Changed 4 years ago by pde

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi, Bill Buddington <bill@eff.org> will be doing some HTTPS Everywhere
maintenance work for EFF.

His PGP key is:
pub   2048R/6842C592 2015-06-01 [expires: 2020-05-30]
      Key fingerprint = 977A 04EC 512A 9D0D B4A5  6E0E CDCA E8ED 6842 C592
uid                  William Budington <bill@inputoutput.io>
uid                  William Budington <bill@eff.org>
sub   2048R/78C30765 2015-06-01 [expires: 2020-05-30]
sub   2048R/E1368FB5 2015-06-01 [expires: 2020-05-30]

I believe his preferred username is "legind".
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWslWuAAoJEElPIbnWfE0hSMwP/0Z5WHECGwWChBsyLfXjqXUD
avB5BgWxLub11Wf6HocwU1BP8YUc71ByON7pCHH24MdmWdKf1VZ16DYoSq6yrasB
29txu6CdVpweNWLm3ATSBBBMkxVlI0YGS0tNC+DRz4laFULVfy04PemukvETisR0
kIshrUNo1mNqc6LE4lJQJH0PbTT/ykFDFLSc5Nb26qP7jYhgrpr4Q3XUqS6Lehgm
l9lbMVylTUPEvrJFWibo4hMkn0v95jxuRFk40MfR0bfK4PaP2Xq821JoWIEw964H
aRAfkh71Li4QlqnY0/HjMfT8IwZogUKwtjnAWBLPKQ6wgnFhSwFYRXPpPD8Q9cFB
VgR0fscZuB7aRbqUMEd8zVRw3P1jVL6pT1X3JmIE5xuK7fmAPcz5ebPW/HS4Jga0
xZiiAY/SlnmtKDeI0Sdf47DSjw4ovThA1NQIXu8ycAB8CWN5I1VZPEt0l7H4NqdH
nsSWOryVbIWwU2AbytDPiIHNvqC28PpLtvuiPSzkm2eHGz4qB0NH04nfBePaWt65
KX4LaMIkDrY/9n89taxhzzb7liTDbpotVvaybhZQphTEA1Ov0teRVnF1U0eO/jTo
AW7/xcaTAzgNjKayBo025ufkNjfi2OQfFwyQ9u29yl9hzcl0ZamqsPR6354NI+5U
gINArgmXQbGeumpsYEZT
=YcOM
-----END PGP SIGNATURE-----

comment:4 Changed 4 years ago by arma

Sounds good to me.

(pde: should we retire some of the old, no longer used, ldap accounts that were made for https-everywhere maintenance? Assuming some of them are no longer used?)

comment:5 Changed 4 years ago by weasel

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.