Opened 4 years ago

Closed 3 years ago

#17853 closed defect (fixed)

review ed25519 document for dirauths (and curious relay ops)

Reported by: Sebastian Owned by: sebastian
Priority: Medium Milestone: Tor: 0.2.8.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: TorCoreTeam201605
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor: SponsorU-can


I wrote a few things which I'd like to have checked for accuracy, at

Child Tickets

Change History (11)

comment:1 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-final

comment:2 Changed 4 years ago by nickm

Status: newneeds_review

comment:3 Changed 3 years ago by mikeperry

Status: needs_reviewneeds_revision

I am fairly confused by this document. It starts and ends with a warning about #17668, gives some instructions about how to use offline keys properly with dirauths to avoid online keys and/or duplicate keys, but doesn't tell me if this process will work around #17668 or not. Will it?

I also think the background information needs to be more clearly separated from the minimum TL;DR summary of how to safely upgrade to 0.2.7.x and properly manage both sets of offline keys (the ed25519 one and the dirauth consensus identity), or there will be risk for confusion and error.

This probably should also be on a pad, so that commenting on specific sections is easier.

comment:4 Changed 3 years ago by Sebastian

Ah. The warning is so that dirauth ops don't upgrade their relay thinking it's OK to do so just because I wrote that text. I hate pads, I cannot work with them, but I've copied the text to and will grab the text from there so I can properly diff it.

comment:5 Changed 3 years ago by nickm

Sponsor: SponsorU-can

comment:6 Changed 3 years ago by nickm

Keywords: TorCoreTeam201605 added

These 0.2.8 items really should get handled in May. Or earlier.

comment:7 Changed 3 years ago by nickm

Calling all non-needs_information tickets for May.

comment:8 Changed 3 years ago by nickm

Owner: set to sebastian
Status: needs_revisionassigned

comment:9 Changed 3 years ago by nickm

Status: assignedneeds_revision

comment:10 Changed 3 years ago by Sebastian

Nobody commented on this, which is the only revision I can reasonably make. I think it's better to have this document than not have it.

comment:11 Changed 3 years ago by Sebastian

Points: nickm1
Resolution: fixed
Status: needs_revisionclosed
Note: See TracTickets for help on using tickets.