@@ -111,7 +111,7 @@ has helpful information about what you need to know to hack on Tor!
We use doxygen to generate documentation in html out of our comments on the
code. We keep an up-to-date version of the generated documentation
code. We keep an up-to-date version of the generated documentation
online at [https://src-ref.docs.torproject.org](https://src-ref.docs.torproject.org/tor/index.html).
This documentation should cover the overall code structure, data structures, and individual functions. It's a work in progress, but we hope it'll be useful to you.
...
...
@@ -199,8 +199,28 @@ Security Releases
* define scope for MVP
* what could be a reasonable timeline?
* by the end of the year have a client (milestones B and C completed)
* MILESTONE B: Secure minimal client
* MILESTONE B: Secure minimal client
* Guard nodes <--- first thing to work on
* Correct path selection <-- important but current restrictions have issues
* Timeouts
* Circuit timeout logic
* Connection timeout logic.
* What other kinds of timeouts?
* Connection padding <-- not necessary
* Circuit padding (with padding machines)
* Build preemptive circuits <-- very important
* Change behavior depending on network parameters
* CBT logic?
* Pathbias logic <-- it can be dropped
* Figure out where to put a specific async executor and/or TLS implementation in our stack.
* MILESTONE C: Client feature parity
* V3 onion services
* Fairness on circuits/streams?
* Support for using bridges
* Pluggable transport support
* Controller API?
* Dormant mode?
* Transparent proxy mode(s)
* Technical debt
* Tooling: CI
* Transition to arti is the best way to tackle technical debt right now.
