Opened 4 years ago

Closed 3 years ago

#19301 closed enhancement (fixed)

Accept Ed25519 identities in EXTEND2 cells

Reported by: nickm Owned by: nickm
Priority: Medium Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop220, ed25519, tor-crypto-identity, tor-ed25519-proto, TorCoreTeam201609, nickm-deferred-20161005
Cc: Actual Points:
Parent ID: #15056 Points: 2
Reviewer: Sponsor: SponsorU-must

Description

Once we have the link-connection part of prop220 implemented, we can start here, and allow relays to start accepting Ed25519 identities in their extend2 cells.

We'll have to update extend_cell_parse to handle these, and extend_cell_t to contain them.

We'll have to update channel_get_for_extend to look up by the complete set of link specifiers.

We'll have to update channel_connect_for_circuit to accept an ed25519 ID, if it hasn't already.

And we'll have to update circuit_extend to handle all that properly.

Child Tickets

Change History (6)

comment:1 Changed 4 years ago by nickm

Points: → 2

comment:2 Changed 4 years ago by nickm

Component: - Select a component → Core Tor/Tor
Keywords: prop220 ed25519 tor-crypto-identity tor-ed25519-proto added
Milestone: → Tor: 0.2.9.x-final
Owner: set to nickm
Sponsor: → SponsorS-must
Status: new → assigned

comment:3 Changed 4 years ago by nickm

Sponsor: SponsorS-must → SponsorU-must

comment:4 Changed 3 years ago by nickm

Keywords: TorCoreTeam201609 added

comment:5 Changed 3 years ago by nickm

Keywords: nickm-deferred-20161005 added
Milestone: Tor: 0.2.9.x-final → Tor: 0.3.0.x-final

Deferring big/risky-feature things (even the ones I really love!) to 0.3.0. Please argue if I'm wrong.

comment:6 Changed 3 years ago by nickm

Resolution: → fixed
Status: assigned → closed

This did get implemented on the #15056_wip branch in september.

Note: See TracTickets for help on using tickets.