aboutsummaryrefslogtreecommitdiff
path: root/crates/arti-client
Commit message (Collapse)AuthorAgeFilesLines
...
* arti-client: Store a handle to the DirMgrStore in TorClient (fmt)Ian Jackson2022-11-151-1/+6
| | | | rustfmt only.
* arti-client: Store a handle to the DirMgrStore in TorClientIan Jackson2022-11-151-1/+4
| | | | We'll need this shortly.
* arti-client: Store a handle to the guardmgr in TorClientIan Jackson2022-11-151-1/+5
| | | | We'll need this shortly.
* Merge branch 'guardmgr' into 'main'Ian Jackson2022-11-142-3/+17
|\ | | | | | | | | Move guardmgr creation to arti-client, rather than within circmgr See merge request tpo/core/arti!850
| * Move GuardMgr::new call to arti_client::TorClient (fmt)Ian Jackson2022-11-141-4/+8
| | | | | | | | rustfmt only, broken out to ease review.
| * Move GuardMgr::new call to arti_client::TorClientIan Jackson2022-11-142-1/+11
| | | | | | | | | | | | | | Having this done within circmgr was irregular - most of our other key buildup functions are done in TorClient::create_inner. It is also inconvenient, as it buries the guardmgr within the circmgr.
* | Merge branch 'store3' into 'main'Ian Jackson2022-11-142-4/+9
|\ \ | | | | | | | | | | | | dirmgr: Expopse DirMgrStore See merge request tpo/core/arti!851
| * | dirmgr Store: Have constructors take DirMgrStoreIan Jackson2022-11-142-4/+9
| |/ | | | | | | | | | | | | Now the Store is constructed by arti_client, solving the problem described here https://gitlab.torproject.org/tpo/core/arti/-/issues/631#note_2853665 but in a different way.
* / bump rust-version to 1.60 in every crate.Nick Mathewson2022-11-101-1/+1
|/
* Check more targetstrinity-1686a2022-11-102-3/+7
|
* Spelling fixes and normalizations on some high-level cratesNick Mathewson2022-11-072-3/+3
|
* guardmgr config: Provide bridge information to new and reconfigureIan Jackson2022-11-031-2/+36
|
* bridges config: Check that bridges aren't enabled with no bridgesIan Jackson2022-11-031-1/+32
| | | | This is the validation which is called for by the documentation.
* guardmgr config: Introduce and require new GuardMgrConfig traitIan Jackson2022-11-031-0/+1
| | | | | It doesn't seem to me like it makes sense to provide the backward compatibility here.
* Run add_warnings.Nick Mathewson2022-11-031-0/+1
|
* Require derive_more 0.99.3Ian Jackson2022-11-031-1/+1
| | | | | | | | 0.99.[012] have a bug https://github.com/JelteF/derive_more/issues/114 which makes the Deref derive for bridgedesc::StateGuard not work and therefore breaks minimal-versions CI. It seems simpler to require the newer version everywhere.
* Merge branch 'readmes' into 'main'Nick Mathewson2022-10-122-241/+4
|\ | | | | | | | | | | | | Abolish maint/readme and use doc include Closes #603 See merge request tpo/core/arti!768
| * cargo fmt to remove blank linesIan Jackson2022-10-121-1/+0
| | | | | | | | | | | | | | Apparently cargo fmt doesn't like these, which my perl rune didn't delete. This commit is precisely the result of `cargo fmt`.
| * Replace all README copies in src/lib.rs with includesIan Jackson2022-10-121-237/+1
| | | | | | | | | | | | | | | | The feature we want is `#[doc = include_str!("README.md")]`, which is stable since 1.54 and our MSRV is now 1.56. This commit is precisely the result of the following Perl rune: perl -i~ -0777 -pe 's{(^//!(?!.*\@\@).*\n)+}{#![doc = include_str!("../README.md")]\n}m' crates/*/src/lib.rs
| * README doctests: fix arti-clientIan Jackson2022-10-121-3/+3
| | | | | | | | | | | | | | | | Add ,ignore to ignore three examples that don't actually compile. cargo readme would add these annotations to lib.rs, but the doc include doesn't do stuff like that. pandoc seems to still render the result just fine.
* | struct BridgeConfig: Rename from BridgeIan Jackson2022-10-121-5/+5
|/ | | | Fixes #599
* pt and bridges: Parse configurationIan Jackson2022-10-121-0/+83
|
* Add pt-client and bridge-client features to arti and arti-clientIan Jackson2022-10-123-0/+8
|
* Allow "clippy::single_char_pattern" in tests.Ian Jackson2022-10-124-0/+4
| | | | | | | This lint exists for perf reasons, and this is rarely relevant in tests. Using double quoted str is generally cognitively less burdensome.
* feature-gate some functions requiring PreferredRuntimetrinity-1686a2022-10-051-1/+10
|
* Merge branch 'hostname-validation' into 'main'Nick Mathewson2022-10-032-18/+2
|\ | | | | | | | | Use hostname-validator crate for hostname validation See merge request tpo/core/arti!739
| * Use hostname-validator crate for hostname validationReylaba2022-10-032-18/+2
| |
* | Bump minor version of tor-rtcompat and most of its dependentsNick Mathewson2022-10-031-8/+8
| | | | | | | | | | | | | | (Since the APIs for the `Schedule::sleep*` functions changed, this is a breaking change in tor-rtcompat. Therefore, the Runtime trait in tor-rtcompat is now a different trait. Therefore, anything that uses the Runtime trait in its APIs has also broken.)
* | Bump crates that have had backward compatible API changes.Nick Mathewson2022-10-031-3/+3
| |
* | Merge branch 'fix-nightly-clippy' into 'main'Ian Jackson2022-09-221-0/+2
|\ \ | |/ |/| | | | | Fix nightly clippy See merge request tpo/core/arti!729
| * Apply 1 suggestion(s) to 1 file(s)Ian Jackson2022-09-221-1/+1
| |
| * fix clippy::needless_borrowtrinity-1686a2022-09-101-0/+2
| |
* | enumerate platform with getresuid supporttrinity-1686a2022-09-102-19/+20
|/
* Remove semver.md from arti-1.0.0Nick Mathewson2022-09-071-3/+0
|
* READMEs: Drop stability warning re configIan Jackson2022-09-021-9/+0
| | | | | The referenced ticket is closed and I think the top-level caveats remaining after !717 are sufficient.
* READMEs: Run maint/readmes (to update READMEs from lib.rs)Ian Jackson2022-09-021-1/+2
|
* arti-client README: Say we intend to provide FFIIan Jackson2022-09-021-1/+2
|
* READMEs: arti-client: Remove caveats and add some xrefsIan Jackson2022-09-022-14/+30
|
* Bump crate versions in preparation for Arti 1.0.0 release.Nick Mathewson2022-09-011-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because we want to work more on ensuring that our semver stability story is solid, we are _not_ bumping arti-client to 1.0.0 right now. Here are the bumps we _are_ doing. Crates with "minor" bumps have had API breaks; crates with "patch" bumps have had new APIs added. Note that `tor-congestion` is not bumped here: it's a new crate, and hasn't been published before. ``` tor-basic-utils minor fs-mistrust minor tor-config minor tor-rtcompat minor tor-rtmock minor tor-llcrypto patch tor-bytes patch tor-linkspec minor tor-cell minor tor-proto minor tor-netdoc patch tor-netdir minor tor-persist patch tor-chanmgr minor tor-guardmgr minor tor-circmgr minor tor-dirmgr minor arti-client minor arti-hyper minor arti major arti-bench minor arti-testing minor ```
* Update README.md files with "readmes" tool.Nick Mathewson2022-08-311-1/+5
|
* Merge branch 'safelog_more' into 'main'Ian Jackson2022-08-262-4/+5
|\ | | | | | | | | Apply safelog to more of the things that we log See merge request tpo/core/arti!693
| * arti-client: Treat list of exit ports as sensitive.Nick Mathewson2022-08-252-3/+4
| |
| * arti-client: Downgrade "got a circuit for" message.Nick Mathewson2022-08-251-1/+1
| | | | | | | | | | | | This is not interesting to the user, and violates some of our safe-logging rules (like "Don't log at info for each user request" and "don't log ports").
* | arti: running_as_setuid: fix MacOs buildIan Jackson2022-08-261-2/+2
| | | | | | | | | | libc::getuid and geteuid are marked unsafe, even though I think they could be safe. So the previous code didn't build.
* | tor-config: Replace dir detection with ConfigurationSource enumIan Jackson2022-08-251-6/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/682#note_2830860 And subsequent IRC discussion. Having done the work as per review comments, I don't much like the result. It's quite un-ergonomiuc. If we can't have fs autodetection, I think syntactic autodetection within sources.rs would be nearly as nice. However, I seem to be outvoted. At least the externally visible functionality (of an arti binary, say) is reasonably ergonomic.
* | config watch: Fix and reduce debounce intervalIan Jackson2022-08-251-0/+2
| | | | | | | | | | | | | | | | The parameter to FileWatcher::new is not a polling time fallback; it is a "debounce time". Events are always delayed by at least this much. 10s is much too long for this. 1s is more appropriate.
* | config sources: Read arti.d as well as arti.tomlIan Jackson2022-08-251-5/+10
|/ | | | Fixes #474 aka #271
* Fix setuid testing for MacOSIan Jackson2022-08-251-16/+42
|
* Merge branch 'no_setuid' into 'main'Nick Mathewson2022-08-243-0/+44
|\ | | | | | | | | arti_client: Refuse to build a client if we are setuid. See merge request tpo/core/arti!689
| * arti_client: Refuse to build a client if we are setuid.Nick Mathewson2022-08-243-0/+44
| | | | | | | | | | | | Arti is not designed to be a setuid-safe program. Part of #523.