Changes between Version 2 and Version 3 of org/teams/NetworkTeam/NetworkTeamProducts


Ignore:
Timestamp:
Sep 14, 2017, 8:05:48 PM (10 months ago)
Author:
cypherpunks
Comment:

removing already implemented feature from the "Future" section

Legend:

Unmodified
Added
Removed
Modified
  • org/teams/NetworkTeam/NetworkTeamProducts

    v2 v3  
    1515
    1616|| '''Product''' || '''Who is/are the lead maintainer(s)?''' || ''' Scope''' || '''Status''' || '''Future''' ||
    17 || '''Tor''' || nickm || Tor is the network daemon that makes Tor clients, relays, directories, and authorities run. || Under active development since 2002 or so.  Tor 0.2.7 will come out this fall. || * In the near-term, there are many proposals in the pipeline that would enhance the Tor protocol.[[BR]][[BR]] * We're working on modularizing Tor's design to make it easier to test ,  easier to sandbox components, and easier to write pieces in simpler  languages.[[BR]][[BR]] * Ongoing work to improve crypto throughout the Tor protocol.[[BR]][[BR]] * Ongoing work to improve path selection throughout the Tor protocol[[BR]][[BR]] * Work to improve test coverage throughout Tor daemon.[[BR]][[BR]] * Resist DoS better[[BR]][[BR]] * Write major components in safer languages[[BR]][[BR]] * Remove the leading 0 from the version number[[BR]][[BR]] * Drop TLS?[[BR]][[BR]] * Better resist traffic-analysis attacks.[[BR]][[BR]] * One day, we will merge the Consensus Diffs SOP code.[[BR]][[BR]] * Improve performance throughout code ||
     17|| '''Tor''' || nickm || Tor is the network daemon that makes Tor clients, relays, directories, and authorities run. || Under active development since 2002 or so.  Tor 0.3.2 will come out this fall. || * In the near-term, there are many proposals in the pipeline that would enhance the Tor protocol.[[BR]][[BR]] * We're working on modularizing Tor's design to make it easier to test ,  easier to sandbox components, and easier to write pieces in simpler  languages.[[BR]][[BR]] * Ongoing work to improve crypto throughout the Tor protocol.[[BR]][[BR]] * Ongoing work to improve path selection throughout the Tor protocol[[BR]][[BR]] * Work to improve test coverage throughout Tor daemon.[[BR]][[BR]] * Resist DoS better[[BR]][[BR]] * Write major components in safer languages[[BR]][[BR]] * Remove the leading 0 from the version number[[BR]][[BR]] * Drop TLS?[[BR]][[BR]] * Better resist traffic-analysis attacks.[[BR]][[BR]] * Improve performance throughout code ||
    1818|| '''Tor Specifications/Proposals''' || nickm (with help from atagar, dgoulet and isis.) || * The specifications describe what a program must do to interoperate correctly and safely with Tor clients and relays.[[BR]][[BR]] * The proposals each describe a proposed change to the specifications. || The specifications are mostly accurate, but a bit disjointed:[[BR]][[BR]] * they  haven't received any comprehensive attention for flow since we first  wrote them, mostly.[[BR]][[BR]] * The older proposals are getting stale; Nick used to write a  periodic  "what's new, what are the statuses" document, but that hasn't happened  in a while.[[BR]][[BR]] *  We don't have a real change control process on proposals; perhaps we should. || * See if we can't make the specs more accurate and readable[[BR]][[BR]] * Switch our protocol descriptions to something a bit more rigorous than the plain-english descriptions we use today?[[BR]][[BR]] * Consider a better change-tracking process.[[BR]][[BR]] * See if we can't reinstate regular review of the proposals' status.[[BR]][[BR]] * Try to move more proposals to accepted/rejected.[[BR]][[BR]] * Integrate proposals more quickly ||
    1919|| '''Trunnel[[BR]]'''  https://gitweb.torproject.org/trunnel.git/ || nickm || * Trunnel is a set of python scripts that generate human-readable binary-format parsing/unparsing code. ||  * In use for Tor today. Recommended for use with all new binary formats Tor needs to parse/generate.  || * No current improvements planned.[[BR]][[BR]] * Correctness proof might be nice[[BR]][[BR]] * Might be nice to make it parse TLS.[[BR]][[BR]] * Encourage other protocols to use[[BR]][[BR]] * Rigorously document transformations[[BR]][[BR]] * Support more languages (WTB C++11 support)[[BR]][[BR]] * Fuzzing as a correctness / security check ||