Opened 18 months ago

Closed 2 months ago

#18267 closed enhancement (duplicate)

Enable Exit Policy by Autonomous System Numbers

Reported by: naif Owned by:
Priority: Medium Milestone: Tor: very long term
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #22340 Points:
Reviewer: Sponsor:

Description

This ticket is to improve Tor in a way to enable Exit Policy to be able to accommodate AS numbers, other than just IP addresses/netblocks and ports.

This requirements come up when measuring how to make a Tor Exit Relay that enable connections only to high traffic, but very likely not abuse-generating, websites of major internet destinations.

Assuming that i may wish to make a Tor Exit nodes only for those destinations where we know there's high traffic to be routed trough the Tor Network, but with a limited risks of ISP/Provider takedown due to those large corporations not being automatic-abuse-generating, i tried to collect the numbers of AS for each of the following:
Google (17 AS)
Facebook (1 AS)
Twitter (3 AS)
Microsoft (28 AS)
Yahoo (59 AS)
Wikipedia (3 AS)
Linkedin (9 AS)
Github (1 AS)
Cloudflare (5 AS)

The amount of netblocks part of those AS are a lot and i don't think they will fit the Exit Policy. When it has been tried to load the list of all Italian netblocks (like at #993), weird things happened and it basically didn't worked out.

If Tor servers and clients would become AS-aware, then it would be possible to run a Tor Exit node, deciding to refine an exit policy for very-limited-liability and very-limited-abuse-generating-setup that could probably make it easier to run Tor also on my home broadband line (not being abuse generating destinations, my home ISP won't cut me the subscription!).

That's something that could become a brick of a building block to reach a point where the end-user (Tor Browser users) maybe able to route some traffic out by default (ex: route only the top target AS destinatation that would dynamically enable to offload the "bulk-but-not-abuse-generating" network traffic)

Child Tickets

Change History (4)

comment:1 Changed 18 months ago by cypherpunks

  • Component changed from - Select a component to Tor
  • Type changed from defect to enhancement

This ticket is to improve Tor

comment:2 Changed 18 months ago by naif

Linked discussion A possible way to make end-users to contribute to Tor exit traffic https://lists.torproject.org/pipermail/tor-talk/2016-February/040179.html and related tickets (Make Tor aware of the top-30 destinations of Tor Exit traffic #18268) and (Enable TorBrowser users to become "easy to be run" Tor Exit relay #18269)

comment:3 Changed 12 months ago by nickm

  • Milestone set to Tor: very long term

comment:4 Changed 2 months ago by nickm

  • Parent ID set to #22340
  • Resolution set to duplicate
  • Status changed from new to closed

Reparenting and closing as duplicates of their parent.

Note: See TracTickets for help on using tickets.