Opened 4 years ago

Closed 3 years ago

#17310 closed defect (user disappeared)

PGP Key change

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

Description (last modified by qbi)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

username:andz
old PGP fingerping:7DE3 CA86 49E4 A77C C2CA  6CDC 6579 1E7E 0DB6 0F11
new PGP fingerping:8FD5 CF5F 39FC 03EB B382  7470 5FBF 70B1 D126 0162
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJWF9KHAAoJELhpR+6jUmg3EpkP/3/zVqW+2eBXtT8ji06QMYLX
MijZ84azgAP1jSm92kRUGjDJ5xlxq04BQndiAM43jyEZ9c5EEMb4hhhsBjs5ccx8
NM8MdJMdpZp93EH6uqVSkH3jK86sAtn5h3chVHzkr3bDcbaFNU4NYy4D/D+8SJYe
gned6e0jKP5KcuxfSfd5HQzAXlvOLc6enIRcotlC0GYCiUdUPc4LmL3KRYq4Vml4
Nzq1SGxL5d1ZV/Xj50V9+8f37pFF3UCCegYu43Bccl0cfrJorFVv69h4H8/4LMl8
LuLmc93KKOuhNAoaNZQAtaNB4hX4UfIDGpKDEbRQFu67wTIqeVI57GUz3ULBz4Ne
jqLnnW2OFxlDebAA2RzfgKaUIgwet70P8GQFrX/xqI3GOZR9MhkHawsGiblaiwMw
bmoS4Fb89c5aTMJc12KS5sVCYja3Oh+Gkeh5wAN+kmqrdJ1cc9xqWUVVrHk0Hg95
1Z2FRg0lwe3j1Oy61DDq2vl8EE4iky6w7GikryG9aSH+Sp89zxllD/fEjozuiiJO
3zGhGwi4WW+SjxaHmLcssCki1rMz6CIZj0KTj8Ay4xfgv1VlPFURjAmrSL9jMJO8
QiTlV28heaBJU9FQy6j4QuSDu86g7sGZKsjvU2NoTV3ABi0Hj0Ysju0w2TZxwgzb
k+whxb46vHmH2zMRNpNf
=vANj
-----END PGP SIGNATURE-----

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by qbi

Description: modified (diff)
Severity: Normal

Your key currently has no signatures on it. Try to aquire some signatures from other members of the Tor project and ping us again. We'll change your key then.

comment:2 Changed 4 years ago by anadahz

Why does it need signatures on it?

According to this https://help.torproject.org/tsa/doc/accounts/#key-rollover

If you are planning on migrating to a new PGP key and you also want to change your key in LDAP, you need to create a ticket in trac in the Tor Sysadmin Team component:
    The ticket should include your username, your old PGP fingerprint and your new PGP fingerprint.
    The ticket should be PGP signed with your PGP key that is currently stored in LDAP.

comment:3 Changed 4 years ago by weasel

You don't /have/ to, but we prefer that keys be connected to the web of trust. Your new key isn't even signed by your old key.

comment:4 in reply to:  3 Changed 4 years ago by anadahz

Replying to weasel:

You don't /have/ to, but we prefer that keys be connected to the web of trust. Your new key isn't even signed by your old key.

If this not a hard requirement please proceed with the ticket.
Thanks!

comment:5 Changed 4 years ago by weasel

Status: newneeds_revision

I'll put it on hold for now.

comment:6 in reply to:  5 Changed 4 years ago by anadahz

Replying to weasel:

I'll put it on hold for now.

Why on hold?

comment:7 Changed 4 years ago by anadahz

Can I pass a signed version of the key to the sysadmin team without publicly upload it?

comment:8 Changed 3 years ago by weasel

Resolution: user disappeared
Status: needs_revisionclosed

TTL exceeded.

Note: See TracTickets for help on using tickets.