Opened 7 months ago

Closed 7 months ago

#20552 closed enhancement (implemented)

Advertise support for ed25519 link handshake using subprotocol versions

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: TorCoreTeam201611
Cc: Actual Points: 0
Parent ID: #15054 Points: .5
Reviewer: Sponsor: SponsorU-must

Description

Now that #15055 is merged, #15056 will want to know which relays support its link protocol extensions. But to do that, we'll need to expose the fact in descriptors. The canonical way to do that is now with subprotocol versions (see prop#264).

Child Tickets

Change History (4)

comment:1 Changed 7 months ago by nickm

  • Points set to .5
  • Sponsor set to SponsorU-must

comment:2 Changed 7 months ago by nickm

  • Actual Points set to 0
  • Keywords TorCoreTeam201611 added
  • Status changed from new to needs_review

My branch feature20552 has the code here. Much easier than I thought. Need to think about how this works for bridges, though.

comment:3 Changed 7 months ago by teor

  • Status changed from needs_review to merge_ready

This looks good to me, let's get it merged.

I assume we're not going to recommend LinkAuth 3 in the consensus for a while?
Should we open a ticket for that?

comment:4 Changed 7 months ago by nickm

  • Resolution set to implemented
  • Status changed from merge_ready to closed

Merged!

I assume we're not going to recommend LinkAuth 3 in the consensus for a while?

Right. If we made it recommended, we would be saying "We don't think you should run any Tor before 0.3.0.1-alpha".

Should we open a ticket for that?

I think that every release or two, we should look over the list of recommended protocols en toto, and see if there's anything we should add or remove.

Note: See TracTickets for help on using tickets.