Changes between Version 6 and Version 7 of org/sponsors/SponsorV


Ignore:
Timestamp:
Oct 25, 2017, 2:24:09 AM (2 years ago)
Author:
mikeperry
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • org/sponsors/SponsorV

    v6 v7  
    1717= Tentative Roadmap =
    1818
    19 Guard discovery attacks are currently believed to be the most serious threat to anonymity and availability of the Tor network. The full scope and vectors for these attacks are not yet fully understood, but we are collecting tickets for the [https://trac.torproject.org/projects/tor/query?keywords=~guard-discovery most severe vectors].
     19We 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 [https://trac.torproject.org/projects/tor/query?keywords=~guard-discovery these vectors under the keyword guard-discovery].
    2020
    2121This 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.
     
    2323== Short Term ==
    2424
    25 Our 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.
     25Our 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.
    2626
    2727The set of development work for this is:
     
    3737== Long Term ==
    3838
    39 After 0.3.3,
     39After 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.
    4040
    41 === Research Roadmap ===
     41XXX: These two simulators should have tickets.
    4242
     43Proposal 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. [https://www.cypherpunks.ca/~iang/pubs/conflux-pets.pdf 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.
     44
     45=== Research Topics ===
     46
     47As 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.
     48
     49XXX: I'm sure there are other things we need researched also.