Closed
Milestone
Jun 23, 2021–Nov 1, 2021
Arti 0.0.1 release: basic anonymity
The criteria for an 0.0.1 release is that it has all the pieces needed for basic anonymity.
4 months to complete
Proposal: https://forum.zcashcommunity.com/t/arti-a-pure-rust-tor-implementation-for-zcash-and-beyond/38776
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
60
- Rework `arti` CLI to use a subcommand-capable argument parser
- Try to make test_builder reliable.
- tor-guardmgr: handle unlisted guards correctly
- The 'pending' flag is not cleared on a consensus correctly in all cases
- Update release process and release Arti 0.0.1
- Revise README and similar to describe new status
- Collaborative multiprocess interaction: the cheap version
- 'tokio-runtime-worker' panicked at 'Couldn't get a listed relay?!'
- Panic due to Too many open files (os error 24)
- Investigate "path bias lite" for guards that fail too many circuits?
- Is it a problem that we pick our guard before we pick an exit?
- Should we future-proof our state files with serde(flatten)?
- Use consistent naming for derive_builder setters
- Stop using "anyhow" outside of the arti crate
- Brainstorm some example programs to ship with arti 0.0.1
- Duplicate Tor's constant-time and small-subgroup-check behavior in ntor code
- Behavior divergence between default() and new() for IsolationToken
- tor_circmgr::usage: Allow requesting a circuit that supports "exiting to some unspecified port"
- use cargo-audit in CI
- Add OSX instructions to contributing.md
- MockSleepRuntime::wait_for doesn't work very well.
- Launch testing circuits for estimating circuit timeouts as appropriate
- Some way to get notification when there are new consensus params
- Persistence for circuit-build-time observations
- Add a function to answer "when did we last get incoming network activity".
- Design a logo for arti
- Autogenerate documentation with --document-private-items too
- Figure out how to get on docs.rs
- Reliable cross-compilation process for android
- Naming issue on `tor-client` crate
- Make tor-rtcompat compileable without any runtimes
- Write a timeline and set of policies for discouraging new features in C tor
- Allow more parties to publish on crates.io
- Refactor ipv[46]_policy accessors in tor_netdir::Relay to account for BadExit
- Replace use of SelectAll<Once<F>> with FuturesUnordered<F>
- Identify crates that should not be tor-specific
- Come up with a workable binary build process
- Arti uses createfast for one-hop directory fetches but it should use create if it can
- Refactor circuit manager to better support correct algorithms
- Refactor and rename tor-retry
- Remove dependencies from the 'arti' crate
- Smaller dirmgr refactorings
- Apply a larger swath of clippy warnings.
- Incorrect Accept-Encoding header when xz or zstd is disabled.
- `tor_rtcompat::test::simple_tls` does not pass on OSX
- Upload an 0.0.0 release.
- Make a separate "arti" crate that has just the CLI.
- API for "ssl connection factory" type
- Abstract "stream-target" API
- Reach 75% test coverage
- Refactor async-backend compatibility layer
- Implement stream isolation
- Implement a mechanism for persistent state
- Implement guard nodes
- Implement full circuit-build-timeout logic
- Start using sementic versioning
- Add a test framework for the path selection algorithm
- Circmgr needs a background job that removes too-dirty circuits
- Circmgr needs a significant backend revision
- Make sure that a circuit doesn't use relays in the same family
Loading
Loading
Loading