updated Tor release key #527
No reviewers
Labels
No Label
Benchmarking and Performance
HTTP Storage Protocol
Nevow Removal
Python 3 Porting
not-for-merge
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tahoe-lafs/tahoe-lafs#527
Loading…
Reference in New Issue
No description provided.
Delete Branch "update-tor-release-key"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Looks like the Tor release key changed, which breaks new runs of integration tests.
Codecov Report
93.93% <0%> (-0.31%)
92.96% <0%> (+0.31%)
90.05% <0%> (+0.52%)
95.53% <0%> (+0.55%)
50.56% <0%> (+0.56%)
95.94% <0%> (+0.95%)
100% <0%> (+2.06%)
91.35% <0%> (+3.7%)
100% <0%> (+8%)
85.36% <0%> (+12.19%)
Continue to review full report at Codecov.
It looks like the key expired on August 30th 2018. So someone updated the expiration date to 2020. The "key" itself is the "same" (same fingerprint, for example) but it has a new signature with the new expiration date.
I guess that apt was unhappy because even though it is the same signing key and the signatures on the packages should still be the same and valid, the key itself that the install script is giving to apt is expired and so apt refuses to respect it.
Thanks. I inspected the new key here with
gpg -v <key
and saw that it has the same fingerprint as the old key and the same fingerprint as the Tor project gives on their own website (https://www.torproject.org/docs/signing-keys.html.en) and I see that the integration tests are now installing the Tor packages and passing.