mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.2 2021-11-29T20:21:58Z 2021-11-29T20:21:58Z Nick Mathewson nickm@torproject.org 2021-11-29T20:21:58Z urn:sha1:eef81d9d570572b7a57a76de4003721c546856de 2021-11-18T16:37:48Z Nick Mathewson nickm@torproject.org 2021-11-17T19:16:55Z urn:sha1:5184f5ba84d76b75022fe6249ba18fe42807b1aa To do this at all neatly, I had to split out `tor-config` from `arti-config` again, and putting the lower level stuff (paths, builder errors) into tor-config. I also changed our use of derive_builder to always use a common error type, to avoid error type proliferation. 2021-10-29T15:05:51Z Nick Mathewson nickm@torproject.org 2021-10-29T15:05:51Z urn:sha1:e6e740646ac61c9f06dc332cc156d4b20e793b70 2021-10-27T18:11:48Z eta tor@eta.st 2021-10-27T16:40:00Z urn:sha1:4fa0122dde2b664ebd10bfbe46da54c396dffdb3 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. 2021-10-24T02:23:26Z Nick Mathewson nickm@torproject.org 2021-10-24T02:23:26Z urn:sha1:89de07686d4463800dc7cd7dc4bdeedc0c400e9a 2021-10-21T18:22:11Z Nick Mathewson nickm@torproject.org 2021-10-21T18:15:13Z urn:sha1:7c7a388e287afa0e168d8d666da6649a5750b9b5 Solves a name conflict with the existing tor_client create. Closes #130. 2021-10-14T17:25:19Z Nick Mathewson nickm@torproject.org 2021-10-14T17:25:19Z urn:sha1:81a5675c1b46adf487c6b19c73018fab6953f295 The default soft limit is typically enough for process usage on most Unixes, but OSX has a pretty low default (256), which you can run into easily under heavy usage. With this patch, we're going to aim for as much as 16384, if we're allowed. Fixes part of #188. 2021-10-14T17:12:58Z Nick Mathewson nickm@torproject.org 2021-10-14T17:12:58Z urn:sha1:0cb723164954d99e5ad3b5a952a8dcdf4f413b1d I don't love this approach, but those errors aren't distinguished by ErrorKind, so we have to use libc or winapi, apparently. At least nothing here is unsafe. Addresses part of #188. 2021-10-09T23:37:08Z Nick Mathewson nickm@torproject.org 2021-10-09T23:37:08Z urn:sha1:dcca0ec36638032475be359012eb473b86447e28 I tried using -Z minimal-versions to downgrade all first-level dependencies to their oldest permitted versions, and found that we were apparently depending on newer features of all three crates. I'm kind of surprised there were only three. 2021-10-09T21:30:06Z Nick Mathewson nickm@torproject.org 2021-10-09T21:21:45Z urn:sha1:58355d7d54acaa1057c0a375affdf766d54a0c37