Opened 4 years ago

Last modified 7 weeks ago

#17548 assigned defect

https://bridges.torproject.org/keys shows outdated keys

Reported by: gk Owned by:
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Normal Keywords: ex-sponsor-19
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor: Sponsor30-can

Description (last modified by gk)

While looking at ​https://bridges.torproject.org/keys that the online keys expired 2015-09-11. It seems the document needs an update. And s/will will not/will not/.

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by gk

Description: modified (diff)

comment:2 Changed 11 months ago by sysrqb

Closed #20498 as a dupe

comment:3 Changed 11 months ago by gaba

Owner: isis deleted
Points: → 1
Sponsor: → Sponsor19
Status: new → assigned

comment:4 Changed 11 months ago by arma

another approach besides updating the key might be to figure out what the key is actually used for, notice that it hasn't been working for three+ years and nobody minded, and change the design to not need this key anymore.

comment:5 Changed 6 months ago by gaba

Keywords: ex-sponsor-19 added

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

comment:6 Changed 6 months ago by phw

Sponsor: Sponsor19 → Sponsor30-can

Moving from Sponsor 19 to Sponsor 30.

comment:7 Changed 2 months ago by phw

BridgeDB is (or was) able to sign its email distributor's responses. As far as I can tell, the feature no longer works. I suggest to remove the feature: it's quite a bit of complexity that currently serves no purpose. If somebody ever wants to resurrect it, it will still be part of our commit log.

comment:8 Changed 7 weeks ago by phw

For what it's worth, BridgeDB's log files suggest that it occasionally gets requests for the PGP keys. This happened several times in today's logs. We should spend one or two hours trying to figure out if we can update these keys.

Note: See TracTickets for help on using tickets.