Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#19649 closed enhancement (duplicate)

Define a link specifier containing an ntor onion key

Reported by: teor Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs, 030-proposed, prop224
Cc: Actual Points:
Parent ID: #17238 Points: 3
Reviewer: Sponsor:

Description

If we want to support intro and rend points that aren't in the consensus, we need to define and parse a link specifier with an ntor onion key in it.

In order to extend via ntor to an introduction point, either:

  • the introduction point must be in the consensus, and have an ntor onion key in its descriptor, or
  • the HS descriptor must contain the ntor onion key for the introduction point

In order to extend via ntor to a rendezvous point, either:

  • the rendezvous point must be in the consensus, and have an ntor onion key in its descriptor, or
  • the INTRODUCE2 cell must contain the ntor onion key for the rendezvous point

Child Tickets

Change History (5)

comment:1 Changed 3 years ago by teor

Oh, we should also deprecate the TAP onion key in the link specifier in the prop224 spec. There should be no TAP keys in the new spec.

comment:2 Changed 3 years ago by nickm

I thought that we *did* have a described link specifier type for this in prop220 ? (I really really hope I can finish the implementation soon; see #15055 and its children)

comment:3 Changed 3 years ago by teor

Resolution: duplicate
Status: newclosed

Sorry, I was reading prop224, which referenced tor-spec.txt, which didn't have the ed25519 specifier.

comment:4 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 3 years ago by nickm

Milestone: Tor: 0.3.???

Milestone deleted

Note: See TracTickets for help on using tickets.