- Rust 96.4%
- Python 1.7%
- Shell 1%
- RenderScript 0.4%
- C 0.4%
|
|
||
|---|---|---|
| .gitlab/issue_templates | ||
| arti-corpora@fc8b082577 | ||
| crates | ||
| debian | ||
| doc | ||
| examples | ||
| maint | ||
| python | ||
| tests | ||
| web | ||
| .appveyor.yml | ||
| .ecrc | ||
| .editorconfig | ||
| .flake8 | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .mailmap | ||
| .typos.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| clippy-nightly.toml | ||
| clippy-nontest.toml | ||
| clippy.toml | ||
| CODE_OF_CONDUCT | ||
| CONTRIBUTING.md | ||
| flake.lock | ||
| flake.nix | ||
| GPL-3 | ||
| LGPL-3 | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
| tomlfmt.toml | ||
| WANT_FROM_OTHER_CRATES | ||
Arti: reimplementing Tor in Rust
Arti is a project to produce an embeddable, production-quality implementation of the Tor anonymity protocols in the Rust programming language.
Links:
This is the README for the Arti project as a whole. If you want to find more practical information you might want to check out these links:
-
The README for the
artibinary crate, which includes instructions for how to run Arti with Tor Browser.
Why rewrite Tor in Rust?
Rust is more secure than C. Despite our efforts, it's all too simple to mess up when using a language that does not enforce memory safety. We estimate that at least half of our tracked security vulnerabilities would have been impossible in Rust, and many of the others would have been very unlikely.
Rust enables faster development than C. Because of Rust's expressiveness and strong guarantees, we've found that we can be far more efficient and confident writing code in Rust. We hope that in the long run this will improve the pace of our software development.
Arti is more flexible than our C tor implementation. Unlike our C tor,
which was designed as SOCKS proxy originally, and whose integration features
were later "bolted on", Arti is designed from the ground up to work as a
modular, embeddable library that other applications can use.
Arti is cleaner than our C tor implementation. Although we've tried to develop C tor well, we've learned a lot since we started it back in 2002. There are lots of places in the current C codebase where complicated "spaghetti" relationships between different pieces of code make our software needlessly hard to understand and improve.
Current status
Arti can connect to the Tor network, bootstrap a view of the Tor directory, and make anonymized connections over the network. Now that Arti has reached version 1.0.0, we believe it is suitable for actual use to anonymize connections.
There are a number of areas (especially at the lower layers) where APIs
(especially internal APIs) are not stable,
and we are likely to change them.
Right now that includes the command line interface to the arti program.
And of course it's still very new so there are likely to be bugs.
Building and using Arti
Arti can act as a SOCKS proxy that uses the Tor network.
We expect to be providing official binaries soon. But, for now, you need to obtain a Rust development environment, and build it yourself.
To try it out, compile and run the arti binary using the below. It will open a
SOCKS proxy on port 9150.
$ cargo run -p arti --locked --release -- proxy
You can build a binary (but not run it) with:
$ cargo build -p arti --locked --release
The result can be found as target/release/arti.
⚠ Safety Note: if you are using the default build options,
the compiler will include filesystem path information in the
binary that it generates. If your path is sensitive (for example,
because it includes your username), you will want to take steps
to prevent this. See doc/safer-build.md
for more information.
⚠ Safety Note: when building arti for "production use",
you should always use the -p arti option as documented above.
While a cargo build without specifying the -p arti will still build arti,
it may also enable unintended features (including experimental features)
due to cargo feature unification.
If you run into any trouble building the program, please have a look at the troubleshooting guide.
Custom compile-time options
Arti has a number of configurable Cargo features that, among other things, can affect which asynchronous runtime to use.
See in the Arti crate-level docs for details.
Using Arti as a library
The arti command line utility is built on top of the
arti_client
library (and its dependencies).
That library's API will allow you to make connections over the Tor network, and obtain streams/sinks usable from async Rust.
We make fairly frequent semver bumps to the Arti library API,
and to our lower-level crates.
However, in practice, we don't often make disruptive changes
that aren't easy to sort out in a dependency.
When using Arti as a library, you should be prepared to make regular updates,
bumping your versions requirement, not just cargo update.
cargo upgrade can help with this.
See our version update and API compatibility policy for more details.
Minimum supported Rust Version
Our current Minimum Supported Rust Version (MSRV) is 1.89.
We may increase this MSRV as new Rust versions become available from the upstream Rust project. We allow upgrades of our MSRV to Rust X.Y.Z if Rust X.Y.0 was released within the last 7 months.
We won't increase MSRV just because we can: we'll only do so when we have a reason. (We don't guarantee that you'll agree with our reasoning; only that it will exist.)
How can I report bugs?
When you find bugs, please report them on our bugtracker.
If you don't already have an account there, you can report a bug anonymously or you can request an account.
How can I help out?
Have a look at our contributor guidelines for a few ideas on how to get started.
License
This code is licensed under either of
at your option.
However, some optional parts are licensed under the GNU Lesser General
Public License, version 3.0,
as indicated in the Cargo.toml.
This applies to crates/equix and crates/hashx.
See LGPL-and-rust.md
for discussion of issues concerning redistributing binaries
containing these crates.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
(The above notice, or something like it, seems to be pretty standard in Rust projects, so I'm using it here too. This instance of it is copied from the RustCrypto project's README.md file.)