| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
It is now a (conditional, experimental) dependency of arti-client.
|
| |\
| |
| |
| |
| | |
Bump versions for today's release of arti 1.1.3
See merge request tpo/core/arti!1102
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These crates had no changes until just a moment ago. But since
we updated the versions on some of their dependents, they have now
changed themselves. Thus they get patchlevel bumps.
```
tor-rtmock
tor-protover
tor-socksproto
tor-consdiff
tor-chanmgr
tor-dirclient
tor-hsservice
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These crates have had breaking changes. They are pre-1.0, so they get
a minor bump.
```
tor-basic-utils
tor-config
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For these crates, the changes are nontrivial, so we
_do_ bump the versions on which their dependent crates depend.
Fortunately, since they are all pre-1.0, we don't need to
distinguish semver-additions from other changes. (Except for arti,
which _is_ post-1.0, but gets a patchlevel bump anyway.)
These are unstable crates with breaking changes:
```
tor-hscrypto
tor-hsclient
```
These have new or extended APIs:
```
safelog
tor-bytes
tor-cell
tor-linkspec
tor-llcrypto
tor-proto
tor-cert
arti-client
```
These have new unstable APIs or features:
```
tor-netdoc
tor-circmgr (also broke some unstable APIs)
arti (is post-1.0)
```
These have bugfixes only:
```
caret
tor-dirmgr
```
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Their dependents are _not_ updated to a more recent version.
These bumped the version of a dependency that they don't expose
```
tor-rtcompat
fs-mistrust
```
This one had internal refactoring:
```
tor-netdir
```
These had trivial changes only:
```
tor-checkable
tor-ptmgr
tor-guardmgr
arti-hyper
arti-bench
arti-testing
```
|
| | |
|
| | |
|
| |
|
|
| |
(We don't include Tor employees in our "thanks" section.)
|
| | |
|
| |\
| |
| |
| |
| | |
tor-hsclient: Fix a doc link.
See merge request tpo/core/arti!1101
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Run cargo update in preparation for release tomorrow.
See merge request tpo/core/arti!1100
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Fix broken doc link.
See merge request tpo/core/arti!1082
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a broken doc link I introduced in !1070:
```
error: unresolved link to `crate::doc::hsdesc::build::inner::HsDescInnerBuilder`
--> crates/tor-netdoc/src/doc/hsdesc/build/middle.rs:34:11
|
34 | /// [`crate::doc::hsdesc::build::inner::HsDescInnerBuilder`] as described in sections
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no item named `HsDescInnerBuilder` in module `inner`
|
= note: `-D rustdoc::broken-intra-doc-links` implied by `-D warnings`
error: could not document `tor-netdoc`
```
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| |\ \
| | |
| | |
| | |
| | | |
More plumbing for hs connections
See merge request tpo/core/arti!1098
|
| | | |
| | |
| | |
| | | |
Apply this churn, which I deferred for ease of review.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
I found that I had the bug where I forgot to call this function, and
reached
bad_api_usage!("The circuit launcher wasn't initialized")
The possibility of such a bug is a hazard of this API pattern.
|
| | | |
| | |
| | |
| | |
| | | |
The old name was unwieldy and other crates can just as well name it by
the crate scope.
|
| | | |
| | |
| | |
| | |
| | | |
Not doing this was a bug. The bug was possible because of some code
duplication between the exit and hs paths. Add a comment about that.
|
| | | |
| | |
| | |
| | |
| | | |
This will be more convenient inside tor-hsclient. In arti-client,
this mirrors the way TorClient::get_or_launch_exit_circ works.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Document some workflow practices
See merge request tpo/core/arti!1079
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
One ref to the official docs, one to a reasonable-looking blog post I
found via DDG.
Suggested in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1079#note_2889631
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The placement in the "Where are some good places to start hacking?"
section is rather awkward, but I didn't see where else to put it.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The placement in the "Where are some good places to start hacking?"
section is rather awkward, but I didn't see where else to put it.
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-circmgr: Make take_or_launch_stub_circuit future Send
See merge request tpo/core/arti!1096
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | | |
thread_rng() isn't Send. We can fix this by not holding it over an
await point.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
tor-netdir: Implement `HsDirRing::find_pos`
See merge request tpo/core/arti!1095
|
| | | | | |
|
| | |/ /
| | |
| | |
| | | |
This eliminates an untyped `usize` index.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Upgrade some dependencies in preparation for tomorrow's release
See merge request tpo/core/arti!1093
|
| | | | | |
|
| |/ / / |
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Move functionality from tor_basic_utils to tor_async_utils
See merge request tpo/core/arti!1091
|
| | | |
| | |
| | |
| | |
| | | |
This commit is mostly code movement; I'd recommend reviewing it
with git's `--color-moved` option.
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
key blinding: Use consistent terminology
See merge request tpo/core/arti!1085
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Don't ever use the words "parameter" or "param".
These doesn't appear in the spec anywhere.
* Use `h` as the variable name for the unclamped blinding factor,
and `blinding_factor` in function names.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Unhelpfully, the spec uses the variable name `h` and the phrase
"blinding factor" for both the unclamped and clamped value. The
clamped value is internal to the algorithm.
In our code:
* Don't ever use the word "parameter" or variable name `param`.
This doesn't appear in the spec anywhere.
* Use `h` for the unclamped blinding factor, and `blinding_factor` for the
clamped blinding factor.
* Rename `blinding_factor` function to `clamp_blinding_factor`, since
in the spec's terminology it takes an (unclamped) "blinding factor"
and returns a (clamped) "blinding factor".
* State explicitly what thing in the spec the `h` parameters are.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Miscellanious tidying up (pursuant to HS client work)
See merge request tpo/core/arti!1086
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now
cargo +stable clippy --locked --offline --workspace --all-targets
is clean.
|
| | | | |
| | | |
| | | |
| | | | |
Obviously it will need this!
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We separated this out in the circmgr API. This is what the HS client
needs. It doesn't want to participate in the general circuit pool.
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now
nailing-cargo +stable clippy -p tor-hsclient --all-features --all-targets
actually works.
squash! Add some missing imports
|