wiki:org/sponsors/SponsorV

Version 8 (modified by mikeperry, 17 months ago) (diff)

--

Timeline

October 2015 - September 2018 (...)

Overview

Joint project with Georgetown and NRL focusing on research about resilience to attacks that reduce anonymity or that deny service.

The grant also includes a "transition to practice" component, which means we should not only help with the research side, but also build and deploy the more promising solutions.

Deliverables

  • Produce research papers
  • Release software (e.g. Tor) that includes fixes based on the research papers
  • Work with Micah Sherr and Rob Jansen

Tentative Roadmap

We currently believe that guard discovery attacks are the most serious threat to anonymity and availability of the Tor network. We are collecting tickets for the these vectors under the keyword guard-discovery.

This roadmap is a living document. We still do not understand the full scope of attacks and fixes for guard discovery attacks, and other attacks that are also in scope of this sponsor may appear at any time. No plan survives contact with the enemy.

Short Term

Our short term plan is to fix lowest hanging fruit first. Because Proposal 247 requires quite a bit of performance tuning, but will still provide improved security without completing that tuning, we are going to aim to support an external implementation through an add-on Tor Controller and torrc options. This Tor controller will also be used for performance evaluation.

The set of development work for this is:

Ticket Resolution Summary Owner Reporter
#13837 implemented Mitigate guard discovery by pinning middle node mikeperry asn
#23100 fixed Circuit Build Timeout needs to count hidden service circuits mikeperry mikeperry
#23101 implemented Predict and build specific HS purpose circuits (rather than GENERAL) mikeperry mikeperry
#23114 implemented Circuit Build Timeout should apply at circuit completion mikeperry mikeperry
#24487 Reverse path selection (choose outer hops first) mikeperry mikeperry

Additionally, a few relatively simple changes can also be completed on the 0.3.2/0.3.3 timescale that should address other vectors relating to our statistics reporting and gathering:

Ticket Resolution Summary Owner Reporter
No tickets found

Ticket Resolution Summary Owner Reporter
No tickets found

Long Term

After 0.3.3, we plan to simulate the performance properties of Prop247 using the addon controller. Separately, we will also simulate the time-until-compromise estimates based on various parameters. We will use the results of these experiments to parameterize Prop247.

XXX: These two simulators should have tickets.

Proposal 247 by itself is insufficient to deal with all forms of guard discovery. In particular, circuit lifetime attacks like #22728 suggest that we need some way of re-establishing cirucits to an IP/RP over a new path. the conflux technique may be one way to do this. Note that for #22728 we do not need the flow control and load balancing pieces of conflux. we only need the ability to migrate an RP/IP from one path to another.

Here are other tickets we do not have a solid plan for yet:

Ticket Resolution Summary Owner Reporter
#22728 Long-lived onion service circuits can enable guard discovery mikeperry
#22729 Revisit relay read/write history resolution (for onion services) mikeperry
#23980 Provide torrc option to kill hidden service circuits after $TIMEOUT, $NUM_BYTES, or guard changes. mikeperry mikeperry
#25574 Eliminate "silent-drop" side channels in Tor protocol mikeperry

Research Topics

As we address passive versions of #22728, we should also determine if the flow control mechanisms of conflux (or some other multipath routing) can provide any benefit against congestion attacks and other forms of denial of service attack against guard nodes.

XXX: I'm sure there are other things we need researched also.