Changes between Version 18 and Version 19 of org/roadmaps/Tor


Ignore:
Timestamp:
Mar 5, 2018, 6:25:40 AM (18 months ago)
Author:
sambhav2612
Comment:

fix grammatical errors

Legend:

Unmodified
Added
Removed
Modified
  • org/roadmaps/Tor

    v18 v19  
    33== Overview ==
    44
    5 The ''tor'' program implements the core client and server code for participating in the Tor network.  The source is available at https://gitweb.torproject.org/tor .
     5The ''tor'' program implements the core client and server code for participating in the Tor network.  The source is available at https://gitweb.torproject.org/tor.
    66
    77== Active Projects ==
     
    1616  * Split AES and SSL across multiple cores. (#1749) (Sponsor D, deliverable 19 for Sep 30: Initial design, maybe code.)
    1717  * Finish integrating a microdescriptor implementation. (#1748) (Sponsor D, deliverable 8 for Sep 30)
    18   * [milestone:"Tor: 0.2.2.x-final" Release candidate for Tor 0.2.2.x.] ([milestone:"Tor: 0.2.2.x-final"]) (Sponsor D, deliverable 18 for Sep 30: release an rc)
     18  * [milestone:"Tor: 0.2.2.x-final" Release candidate for Tor 0.2.2.x.] ([milestone:"Tor: 0.2.2.x-final"]) (Sponsor D, deliverable 18 for Sep 30: release an RC)
    1919  * Add support for bufferevent-based data transports. (#1761)
    2020  * See if we can improve performance by throttling streams at guard nodes (#1750) (Sponsor D, deliverable 2 for Sep 30)
     
    2727
    2828  * Add support for advertising directory mirrors that have no DirPort, but only support BEGIN_DIR.
    29   * Make Tor able to relay more open-formed DNS requests to the exit node's DNS; expand DNSPort to handle TCP dns requests as needed.
     29  * Make Tor able to relay more open-formed DNS requests to the exit node's DNS; expand DNSPort to handle TCP DNS requests as needed.
    3030  * Instrument Tor's internals more thoroughly to identify bottlenecks.
    3131  * Perhaps, make all bridges also able to proxy connections to the Tor download site.
     
    4242    * [Okay. Is this a separate item, or is it the same issue as the lack of a "v" line in response to the controller GETINFO command? -NM]
    4343  * MAYBE kill stalled circuits rather than stalled connections.  This is possible thanks to cell queues, but we need to consider the anonymity implications.
    44   * Make resolves no longer use edge_connection_t unless they are actually _on_ a socks connection: have edge_connection_t and (say) dns_request_t both extend an edge_stream_t, and have p_streams and n_streams both be linked lists of edge_stream_t.
     44  * Make resolves no longer use edge_connection_t unless they are actually _on_ a socks connection: have edge_connection_t and (say) dns_request_t both extend an edge_stream_t and have p_streams and n_streams both be linked lists of edge_stream_t.
    4545  * Generate torrc.{complete|sample}.in, tor.1.in, the HTML manual, and the online config documentation from a single source.
    4646  * It would be potentially helpful to respond to https requests on the OR port by acting like an HTTPS server.
    47   * We should get smarter about handling address resolve failures, or addresses that resolve to local IPs.  It would be neat to retry them, since right now we just close the stream.  But we need to make sure we don't retry them on the same exit as before.  But if we mark the circuit, then any user who types "localhost" will cycle through circuits till they run out of retries.  See bug #872.
     47  * We should get smarter about handling address resolve failures, or addresses that resolve to local IPs.  It would be neat to retry them since right now we just close the stream.  But we need to make sure we don't retry them on the same exit as before.  But if we mark the circuit, then any user who types "localhost" will cycle through circuits till they run out of retries.  See bug #872.
    4848
    4949=== Can anybody remember why we wanted to do this and/or what it means? ===
    5050  * config option `__ControllerLimit` that hangs up if there are a limit of controller connections already.
    51     * [This was mwenge's idea. The idea is that a Tor controller can "fill" Tor's controller slot quota, so jerks can't do cross-protocol attacks like the http form attack. -RD]
     51    * [This was mwenge's idea. The idea is that a Tor controller can "fill" Tor's controller slot quota, so jerks can't do cross-protocol attacks like the HTTP form attack. -RD]
    5252  * Bridge issues:
    5353    * Ask all directory questions to bridge via BEGIN_DIR.
     
    5858=== If somebody wants to do this in some version, they should: ===
    5959  * Create packages for Maemo/Nokia 800/810, requested by Chris Soghoian
    60     * debian already makes ARM-arch debs, can maemo use these asks phobos?
     60    * Debian already makes ARM-arch debs, can maemo use these asks phobos?
    6161  * More work on AvoidDiskWrites
    6262  * Make DNSPort support TCP DNS.
     
    6565  * bridge communities with local bridge authorities:
    6666  * clients who have a password configured decide to ask their bridge authority for a networkstatus
    67   * be able to have bridges that aren't in your torrc. save them in state file, etc.
     67  * be able to have bridges that aren't in your torrc. save them in the state file, etc.
    6868  * Consider if we can solve: the Tor client doesn't know what flags its bridge has (since it only gets the descriptor), so it can't make decisions based on Fast or Stable.
    6969  * Some mechanism for specifying that we want to stop using a cached bridge.
     
    7474  * Our current approach to block attempts to use Tor as a single-hop proxy is pretty lame; we should get a better one.
    7575  * Allow small cells and large cells on the same network?
    76   * Cell buffering and resending. This will allow us to handle broken circuits as long as the endpoints don't break, plus will allow connection (tls session key) rotation.
     76  * Cell buffering and resending. This will allow us to handle broken circuits as long as the endpoints don't break, plus will allow connection (TLS session key) rotation.
    7777  * Implement [http://freehaven.net/anonbib/#morphmix:wpes2002 MorphMix] ([http://freehaven.net/anonbib/#morphmix-fc2004 another paper]), so we can compare its behavior, complexity, etc.  But see [http://freehaven.net/anonbib/#morphmix:pet2006 paper breaking morphmix].
    78   * Other transport. HTTP, udp, rdp, airhook, etc. May have to do our own link crypto, unless we can bully DTLS into it.
     78  * Other transport. HTTP, UDP, RDP, airhook, etc. May have to do our own link crypto unless we can bully DTLS into it.
    7979  * Need a relay teardown cell, separate from one-way ends. (Pending a user who needs this)
    8080  * Handle half-open connections: right now we don't support all TCP streams, at least according to the protocol. But we handle all that we've seen in the wild. (Pending a user who needs this)
     
    8585    * Have a "Faster" status flag that means it. Fast2, Fast4, Fast8?
    8686    * Add an option (related to AvoidDiskWrites) to disable directory caching.  (Is this actually a good idea??)
    87     * `X` Add d64 and fp64 along-side d and fp so people can paste status entries into a url. since + is a valid base64 char, only allow one at a time. Consider adding to controller as well. [abandoned for lack of demand]
     87    * `X` Add d64 and fp64 along-side d and fp so people can paste status entries into a URL. since + is a valid base64 char, only allow one at a time. Consider adding to a controller as well. [abandoned for lack of demand]
    8888    * Some back-out mechanism for auto-approval on authorities
    8989      * a way of rolling back approvals to before a timestamp
    9090        * Consider minion-like fingerprint file/log combination.
    91     * `X` Have new people be in limbo and need to demonstrate usefulness
     91    * `X` Have new people be in limbo and need to demonstrate the usefulness
    9292      before we approve them.
    9393
     
    9696  * you can insert a hidserv descriptor via the controller.
    9797  * auth mechanisms to let hidden service midpoint and responder filter connection requests: proposal 121.
    98   * Let each hidden service (or other thing) specify its own OutboundBindAddress?
     98  * Let each hidden service (or other things) specify its own OutboundBindAddress?
    9999
    100100=== Server operation: ===
     
    106106    * DIR_REACHABLE
    107107    * BAD_DIR_RESPONSE (Unexpected directory response; maybe we're behind a firewall.)
    108     * BAD_PROXY (Bad http or https proxy)
     108    * BAD_PROXY (Bad HTTP or https proxy)
    109109    * UNRECOGNIZED_ROUTER (a nickname we asked for is unavailable)
    110110    * Status events related to hibernation
     
    122122      * import and export rendezvous descriptors
    123123      * Review all static fields for additional candidates
    124     * Allow EXTENDCIRCUIT to unknown server.
    125       * We need some way to adjust server status, and to tell tor not to
    126         download directories/network-status, and a way to force a download.
     124    * Allow EXTENDCIRCUIT to an unknown server.
     125      * We need some way to adjust server status and to tell Tor not to download directories/network-status, and a way to force a download.
    127126      * Make everything work with hidden services
    128127
     
    145144  * Directory guards
    146145  * Mini-SoaT:
    147     * Servers might check certs for known-good ssl websites, and if they come back self-signed, declare themselves to be non-exits.  Similar to how we test for broken/evil dns now.
    148     * Authorities should try using exits for http to connect to some URLS (specified in a configuration file, so as not to make the List Of Things Not To Censor completely obvious) and ask them for results.  Exits that don't give good answers should have the BadExit flag set.
     146    * Servers might check certs for known-good SSL websites, and if they come back self-signed, declare themselves to be non-exits.  Similar to how we test for broken/evil DNS now.
     147    * Authorities should try using exits for HTTP to connect to some URLs (specified in a configuration file, so as not to make the List Of Things Not To Censor completely obvious) and ask them for results.  Exits that don't give good answers should have the BadExit flag set.
    149148    * Alternatively, authorities should be able to import opinions from Snakes on a Tor.
    150149  * Bind to random port when making outgoing connections to Tor servers, to reduce remote sniping attacks.
     
    158157=== Windows server usability: ===
    159158  * Solve the ENOBUFS problem.
    160     * make tor's use of openssl operate on buffers rather than sockets, so we can make use of libevent's buffer paradigm once it has one.
     159    * make tor's use of OpenSSL operate on buffers rather than sockets, so we can make use of libevent's buffer paradigm once it has one.
    161160    * make tor's use of libevent tolerate either the socket or the buffer paradigm; includes unifying the functions in connect.c.
    162   * We need a getrlimit equivalent on Windows so we can reserve some file descriptors for saving files, etc. Otherwise we'll trigger asserts when we're out of file descriptors and crash.
     161  * We need a getrlimit equivalent on Windows so we can reserve some file descriptors for saving files, etc. Otherwise, we'll trigger asserts when we're out of file descriptors and crash.
    163162
    164163=== Documentation: ===
    165   * a way to generate the website diagrams from source, so we can translate them as utf-8 text rather than with gimp. (svg? or imagemagick?)
     164  * a way to generate the website diagrams from source, so we can translate them as UTF-8 text rather than with gimp. (SVG or ImageMagick?)
    166165  * Flesh out options_description array in src/or/config.c
    167   * multiple sample torrc files
    168   * Refactor tor man page to divide generally useful options from less useful ones?
    169   * Add a doxygen style checker to make check-spaces so nick doesn't drift too far from arma's undocumented styleguide.  Also, document that styleguide in HACKING.  (See r9634 for example.)
    170     * exactly one space at beginning and at end of comments, except i guess when there's line-length pressure.
     166  * multiple samples torrc files
     167  * Refactor Tor man page to divide generally useful options from less useful ones?
     168  * Add a Doxygen style checker to make check-spaces so nick doesn't drift too far from arma's undocumented style guide.  Also, the document that style guide in HACKING.  (See r9634 for example.)
     169    * exactly one space at the beginning and at end of comments, except I guess when there's line-length pressure.
    171170    * if we refer to a function name, put a () after it.
    172171    * only write <b>foo</b> when foo is an argument to this function.
    173     * doxygen comments must always end in some form of punctuation.
    174     * capitalize the first sentence in the doxygen comment, except when you shouldn't.
     172    * Doxygen comments must always end in some form of punctuation.
     173    * capitalize the first sentence in the Doxygen comment, except when you shouldn't.
    175174    * avoid spelling errors and incorrect comments. ;)
    176175
    177176=== Packaging: ===
    178177  * The Debian package now uses --verify-config when (re)starting, to distinguish configuration errors from other errors. Perhaps the RPM and other startup scripts should too?
    179   * add a "default.action" file to the tor/vidalia bundle so we can fix the https thing in the default configuration: [https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#PrivoxyWeirdSSLPort">https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#PrivoxyWeirdSSLPort]
     178  * Add a "default.action" file to the Tor/Vidalia bundle so we can fix the https thing in the default configuration: [https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#PrivoxyWeirdSSLPort">https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#PrivoxyWeirdSSLPort]
    180179
    181180== Blue-sky projects ==