Opened 5 years ago

Closed 2 years ago

#11312 closed enhancement (wontfix)

reuse introduction circuit as rendezvous circuit

Reported by: dave2008 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: needs-proposal
Cc: nickm, asn, armadev Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

By using the last hop of introduction circuit as RP, we can save the time spent on creating rendezvous circuit and transmitting establish_rendezvous cells (by combining introduce with establish_rendezvous cell).

A malicious hidden service will be able to link introduction circuit with rendezvous circuit anyway. So at first glance, I don't see any issue.

Child Tickets

Change History (6)

comment:1 Changed 5 years ago by nickm

Keywords: needs-proposal added
Milestone: Tor: 0.2.???

The other issue would be that an introduction point could link the rendezvous circuit with the introduction circtuit, which previously they would not have been able to do.

I haven't analyzed the security implications of that, though. It probably needs a proposal

comment:2 Changed 5 years ago by dave2008

Hm.. good point. That's the case when IP is malicious while HS is not.

I would like to first hack up a demo and do some profiling before sending out a formal proposal. Just to get a rough idea of the performance gain. Then we can discuss on the trade-off between security and speed.

comment:3 Changed 3 years ago by teor

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

Milestone renamed

comment:4 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 2 years ago by nickm

Resolution: wontfix
Severity: Normal
Status: newclosed
Note: See TracTickets for help on using tickets.