| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
We already link to CONTRIBUTING.md near the top of the README in the "Links" section. There's no real need to add two additional links beyond that, especially if they're going to be in very similar looking sections. So we remove one and modify the other to look a little nicer. I've opted to keep the one closer to the end of the README since the top of the README is already covered by the "Links" section.
|
| |
|
|
|
| |
@ahf tells me anonticket is at https://anonticket.torproject.org/
nowadays.
|
| |
|
|
|
|
|
| |
This was disabled due to lack of vanguard support. Now that we support
vanguards, we should enable this by default.
Fixes: #1402
|
| |
|
|
| |
This will allow us to upgrade to the latest version of rusqlite.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Taken from
https://gitlab.torproject.org/tpo/core/arti/-/issues/1005#note_2991812
and edited.
|
| |
|
|
| |
Even before the policy change, this is, in practice, true.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Otherwise our default build instructions will lead people
to build binaries that include their home directory.
Closes #957 for now.
|
| |
|
|
|
| |
Not giving Tor Browser instructions just yet because of the security
caveat.
|
| | |
|
| |
|
|
|
| |
Notably, I'm adding a note to the `arti` README, which includes
information on how to build and use the thing.
|
| | |
|
| | |
|
| |
|
|
| |
See 2c240923fcd0cec75087db39e461ee718228ea14.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- arti#445 highlighted the lack of good documentation around Arti's
multiple runtime support, as well as it being difficult to determine
what runtime was actually in use.
- Improve the documentation to solve the first problem.
- To solve the second problem, make Runtime require Debug (which is
arguably a good idea anyway, since it makes them easier to embed in
things), and print out the current runtime's Debug information when
arti is invoked with `--version`.
- (It also prints out other Cargo features, too!)
fixes arti#445
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Our support policy says that we can update to any Rust released at
least 6 months ago; 1.56 came out on 21 October 2021.
This doesn't yet change any code: it just increases the version
we say we need in our README, and the version we test against in
CI.
Our main justification for this change is to be able to upgrade to
newer versions of our dependencies, including `async_executors` >=
0.5, `aes` >= 0.8, and `cipher` >= 0.4.
|
| |
|
|
| |
Keep http in license text.
|
| | |
|
| |
|
|
|
|
|
| |
Explain how to report bugs and how get accounts on the bugtracker;
add link to the troubleshooting document.
Part of #277
|
| |
|
|
| |
Closes #283.
|
| | |
|
| |
|
|
| |
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This switches out `arti`'s argument-parsing library with `clap`, which
is a lot more featureful (and very widely used within the Rust
ecosystem). We also now use a lot of `clap`'s features to improve the
CLI experience:
- The CLI now expects a subcommand (currently, either "help", or "proxy"
for the existing SOCKS proxy behaviour). This should let us add
additional non-SOCKS-proxy features to arti in future.
- `clap` supports default values determined at runtime, so the way the
default config file is loaded was changed: now, we determine the
OS-specific path for said file before invoking `clap`, so the help
command can show it properly.
- The behaviour of `tor_config` was also changed; now, one simply
specifies a list of configuration files to load, together with
whether they're required.
- That function also way overused generics; this has been fixed.
- Instead of using the ARTI_LOG environment variable to configure
logging, one now uses the `-l, --log-level` CLI option.
(The intent is for this option to be more discoverable by users.)
- The `proxy` subcommand allows the user to override the SOCKS port used
on the CLI without editing the config file.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Solves a name conflict with the existing tor_client create.
Closes #130.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Closes #106
|
| | |
|
| |\ |
|
| | | |
|
| |/ |
|