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


Ignore:
Timestamp:
Mar 5, 2018, 6:36:26 AM (13 months ago)
Author:
sambhav2612
Comment:

remove extra spacing between sentences

Legend:

Unmodified
Added
Removed
Modified
  • org/roadmaps/Tor

    v19 v20  
    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 ==
     
    4141    * [Nick: bridge authorities output a networkstatus that is missing version numbers. This is inconvenient if we want to make sure bridgedb gives out bridges with certain characteristics. -RD]
    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]
    43   * 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.
     43  * 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.
    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? ===
     
    8484    * handle connect-dir streams that don't have a chosen_exit_name set.
    8585    * Have a "Faster" status flag that means it. Fast2, Fast4, Fast8?
    86     * Add an option (related to AvoidDiskWrites) to disable directory caching.  (Is this actually a good idea??)
     86    * Add an option (related to AvoidDiskWrites) to disable directory caching. (Is this actually a good idea??)
    8787    * `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
     
    114114  * Implement missing status event fields:
    115115    * TIMEOUT on CHECKING_REACHABILITY
    116     * GETINFO status/client, status/server, status/general: There should be some way to learn which status events are currently "in effect."  We should specify which these are, what format they appear in, and so on.
     116    * GETINFO status/client, status/server, status/general: There should be some way to learn which status events are currently "in effect." We should specify which these are, what format they appear in, and so on.
    117117    * More information in events:
    118118      * Include bandwidth breakdown by conn->type in BW events.
     
    130130  * separate config options for read vs write limiting. (It's hard to support read > write, since we need better congestion control to avoid overfull buffers there.  So, defer the whole thing.)
    131131  * Rate limit exit connections to a given destination -- this helps us play nice with websites when Tor users want to crawl them; it also introduces DoS opportunities.
    132   * Consider truncating rather than destroying failed circuits, in order to save the effort of restarting.  There are security issues here that need thinking, though.
    133   * Handle full buffers without totally borking
     132  * Consider truncating rather than destroying failed circuits, in order to save the effort of restarting. There are security issues here that need thinking, though.
     133  * Handle full buffers without totally borking.
    134134  * Rate-limit OR and directory connections overall and per-IP and maybe per subnet.
    135135
     
    144144  * Directory guards
    145145  * Mini-SoaT:
    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.
     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.
    147147    * 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.
    148148    * Alternatively, authorities should be able to import opinions from Snakes on a Tor.
    149149  * Bind to random port when making outgoing connections to Tor servers, to reduce remote sniping attacks.
    150150  * Audit everything to make sure rend and intro points are just as likely to be us as not.
    151   * Do something to prevent spurious EXTEND cells from making middleman nodes connect all over.  Rate-limit failed connections, perhaps?
     151  * Do something to prevent spurious EXTEND cells from making middleman nodes connect all over. Rate-limit failed connections, perhaps?
    152152  * DoS protection: TLS puzzles, public key ops, bandwidth exhaustion.
    153153
     
    166166  * multiple samples torrc files
    167167  * 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.)
     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.)
    169169    * exactly one space at the beginning and at end of comments, except I guess when there's line-length pressure.
    170170    * if we refer to a function name, put a () after it.
     
    179179
    180180== Blue-sky projects ==
    181