summaryrefslogtreecommitdiff
path: root/crates/tor-rpc-connect
Commit message (Collapse)AuthorAgeFilesLines
* Bump all the unstable tor- and arti- crates to 0.25.0.Gabriela Moldovan2024-12-021-5/+5
| | | | | | | | | | Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.25.0 done ```
* Bump the versions of the non-{arti-,tor-} crates.Gabriela Moldovan2024-12-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The non-{arti-,tor-} crates are: ``` ./maint/list_crates | rg -v '^(tor|arti)' oneshot-fused-workaround slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error ``` We split them in the following categories: * crates with no changes (no version bumps): ``` maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-' oneshot-fused-workaround: No change. test-temp-dir: No change. caret: No change. ``` * crates that only have non-functional changes (bump the patch version): - slotmap-careful - fslock-guard - hashx - equix - fs-mistrust - safelog - retry-error * crates where APIs were broken (bump minor): None The bumps from this commit were created using this script: ``` PATCH=" slotmap-careful fslock-guard hashx equix fs-mistrust safelog retry-error " for crate in $PATCH; do cargo set-version --bump patch -p $crate; done ```
* Fix several Cargo.tomls to satisfy cargo-sort.Gabriela Moldovan2024-12-021-1/+1
|
* Run fixup-features in preparation for release (fmt).Gabriela Moldovan2024-12-021-1/+10
|
* Run fixup-features in preparation for release.Gabriela Moldovan2024-12-021-1/+1
|
* tor-rpc-connect: Bump thiserror to 2.Gabriela Moldovan2024-11-281-1/+1
|
* connect point: Use new CfgPathResolver api.Nick Mathewson2024-11-191-12/+22
|
* connect point: handle unrecognized auth variants.Nick Mathewson2024-11-193-6/+39
|
* Connect point: Improve robustness against new SocketAddr variantsNick Mathewson2024-11-191-2/+10
|
* connect point: add a test for ConflictingMembers.Nick Mathewson2024-11-191-0/+13
|
* connect-point: Rename Reps to Addresses.Nick Mathewson2024-11-191-7/+7
|
* connect point: Add server support.Nick Mathewson2024-11-192-0/+71
| | | | | ("Server support" here means binding to a socket and reading a cookie file.)
* connect point: Add client support.Nick Mathewson2024-11-193-0/+182
| | | | | ("Client support" here means connecting to a socket and reading a cookie file.)
* connect point: Treat unrecognized auth types as Decline.Nick Mathewson2024-11-191-0/+9
|
* connect points: Validate more correctness propertiesNick Mathewson2024-11-191-4/+23
| | | | | In particular, we only allow binding/connecting to localhost, and we only support None auth for Unix connections.
* connect points: Remember original string addressesNick Mathewson2024-11-192-6/+59
| | | | The cookie authentication protocol will need these.
* rpc-connect: Types for cookie authentication.Nick Mathewson2024-11-193-1/+190
| | | | (Cookie authentication is described in rpc-cookie-sketch.md)
* rpc-connect: Move tempdir() helper to a new moduleNick Mathewson2024-11-193-17/+36
|
* RPC connect points: Facility to load from files.Nick Mathewson2024-11-193-1/+426
|
* connect point: implement FromStr.Nick Mathewson2024-11-191-17/+58
| | | | | | | | | While doing so, tidy up the errors that we detect when parsing a connect point, so that we can differentiate ones that indicate an unsupported connect-point type. This means that fewer types now implement Deserialize; that's probably a good thing.
* tor-connect-point: new crate to manage RPC connect pointsNick Mathewson2024-11-194-0/+447
See doc/dev/rpc-book/src/rpc-connect-sketch.md for details.