A minimal command line program for connecting to the Tor network
(If you want a more general Tor client library interface, use
Currently Arti can can run as a simple SOCKS proxy over the Tor network. It will listen on port 9150 by default, but you can override this in the configuration. You can direct programs to connect via that SOCKS port, and their connections will be anonymized via Tor. Note: you might not want to run a conventional web browser this way. Browsers leak much private information. To browse the web anonymously, we recommend using Tor Browser.
Arti is still advancing rapidly; we are adding features and eventually we hope it will be able to replace C Tor.
(This is not stable; future versions will break this.)
arti uses the
clap crate for command-line
argument parsing; run
arti help to get it to print its documentation.
The only currently implemented subcommand is
arti proxy; try
arti help proxy for a list of options you can pass to it.
arti looks for its configuration files in a platform-dependent
The configuration file is TOML.
For an example see
(a copy of which is in the source tree,
in the Arti repository).
That example config file documents the configuration options.
It is possible to hook up Arti with Tor Browser.
To do so, we will launch arti independently from Tor Browser. Build arti with
cargo build --release. After that launch it with some basic
$ ./target/release/arti proxy -l debug -p 9150
This will ensure that arti sets its SOCKS port on 9150. Now we need to launch Tor Browser and instruct it to use that SOCKS port.
$ TOR_SKIP_LAUNCH=1 TOR_SOCKS_PORT=9150 TOR_SKIP_CONTROLPORTTEST=1 ./start-tor-browser.desktop
$ TOR_SKIP_LAUNCH=1 TOR_SOCKS_PORT=9150 TOR_SKIP_CONTROLPORTTEST=1 /path/to/Tor\ Browser/Contents/MacOS/firefox
Create a shortcut with the
Target set to:
C:\Windows\System32\cmd.exe /c "SET TOR_SKIP_LAUNCH=1&& SET TOR_SOCKS_PORT=9150&& TOR_SKIP_CONTROLPORTTEST=1&& START /D ^"C:\path\to\Tor Browser\Browser^" firefox.exe"
Start in set to:
(You may need to adjust the actual path to wherever you have put your Tor Browser.)
The resulting Tor Browser should be using arti. Note that onion services and bridges won’t work (Arti doesn’t support them yet), and neither will any feature depending on Tor’s control-port protocol. Features not depending on the control-port such as the “New circuit for this site” button should work.
tokio(default): Use the tokio runtime library as our backend.
async-std: Use the async-std runtime library as our backend. This feature has no effect unless building with
--no-default-featuresto disable tokio.
native-tls– Build with support for the
native_tlsTLS backend. (default)
journald– Build with support for logging to the
journaldlogging backend (available as part of systemd.)
dns-proxy(default) – Build with support for proxying certain simple DNS queries over the Tor network.
harden(default) – Build with support for hardening the Arti process by disabling debugger attachment and other local memory-inspection vectors.
full– Build with all features above, along with all stable additive features from other arti crates. (This does not include experimental features. It also does not include features that select a particular implementation to the exclusion of another, or those that set a build flag.)
rustls– build with the rustls TLS backend. This is not included in
full, since it uses the
ringcrate, which uses the old (3BSD/SSLEay) OpenSSL license, which may introduce licensing compatibility issues.
static– Link with static versions of your system dependencies, including sqlite and/or openssl. (⚠ Warning ⚠: this feature will include a dependency on native-tls, even if you weren’t planning to use native-tls. If you only want to build with a static sqlite library, enable the
static-sqlitefeature. We’ll look for better solutions here in the future.)
static-sqlite– Link with a static version of sqlite.
static-native-tls– Link with a static version of
Libraries should not enable these by default, since they replace one implementation with another.
accel-sha1-asm– Accelerate cryptography by using an assembly implementation of SHA1, if one is available.
accel-openssl– Accelerate cryptography by using openssl as a backend.
Note that the APIs enabled by these features are NOT covered by semantic versioning1 guarantees: we might break them or remove them between patch versions.
experimental-api– build with experimental, unstable API support. (Right now, most APIs in the
articrate are experimental, since this crate was originally written to run as a binary only.)
experimental– Build with all experimental features above, along with all experimental features from other arti crates.
There are many missing features. Among them: there’s no onion service support yet. There’s no anti-censorship support. You can’t be a relay. There isn’t any kind of proxy besides SOCKS.
See the repository README file for a more complete list of missing features.
This library crate contains code useful for making a command line program
arti. The API should not be considered stable.
Remember, semantic versioning is what makes various
cargofeatures work reliably. To be explicit, if you want
cargo updateto only make correct changes, then you cannot enable these features. ↩
pub use cfg::ApplicationConfig;
pub use cfg::ApplicationConfigBuilder;
pub use cfg::ArtiCombinedConfig;
pub use cfg::ArtiConfig;
pub use cfg::ArtiConfigBuilder;
pub use cfg::ProxyConfig;
pub use cfg::ProxyConfigBuilder;
pub use cfg::SystemConfig;
pub use cfg::SystemConfigBuilder;
pub use cfg::ARTI_EXAMPLE_CONFIG;
pub use logging::LoggingConfig;
pub use logging::LoggingConfigBuilder;
Configuration for the Arti command line application
Implement a simple DNS resolver that relay request over Tor.
Detect a “ctrl-c” notification or other reason to exit.
Configure tracing subscribers for Arti
Code to adjust process-related parameters.
Code to watch configuration files for any changes.
Implement a simple SOCKS proxy that relays connections over Tor.