Opened 8 years ago

Last modified 2 years ago

#3028 new enhancement

META: Support non-clique topologies on the network

Reported by: tagnaq Owned by:
Priority: Low Milestone: Tor: very long term
Component: Core Tor/Tor Version:
Severity: Normal Keywords: needs-proposal tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

https://lists.torproject.org/pipermail/tor-relays/2011-April/000759.html

See it like a long term feature request :)
(if there is not one yet)

Child Tickets

Change History (5)

comment:1 Changed 7 years ago by nickm

Milestone: Tor: very long term

comment:2 Changed 7 years ago by nickm

Keywords: needs-proposal added

comment:3 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:4 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:5 Changed 2 years ago by nickm

Severity: Normal
Summary: FascistFirewall for tor relaysMETA: Support non-clique topologies on the network

This ticket asked for a way to have a relay that can't connect to other relays on some particular port. But that's just one case of relaxing Tor's clique assumption, which is also required for relays that don't have IPv4 addresses, and relays that can't reach a subset of other relays. Further, we'll need to remove the clique topology assumption in order to scale to a large number of relays without requiring the number of sockets used on each relay to grow proportionally to the size of the network.

We don't actually know how to do this safely right now; it will take a pretty big amount of design work. Naive solutions have the problem that they would make it easier for an adversary to force users into compromised paths by manipulating the network topology.

Note: See TracTickets for help on using tickets.