| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
| |
Done with
```
cargo set-version -p arti --bump patch
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Done with:
```
CRATES="
tor-basic-utils
tor-async-utils
tor-error
tor-config
tor-events
tor-units
tor-geoip
tor-rtcompat
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-hspow
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-relay-selection
tor-congestion
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
"
for crate in $CRATES; do
cargo set-version -p "$crate" 0.17.0
done
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These have all had backward-compatible changes.
Generated with:
```
cargo set-version --bump patch -p fs-mistrust
cargo set-version --bump patch -p test-temp-dir
cargo set-version --bump patch -p fslock-guard
cargo set-version --bump patch -p hashx
cargo set-version --bump patch -p equix
cargo set-version --bump patch -p caret
cargo set-version --bump patch -p safelog
cargo set-version --bump patch -p retry-error
```
|
| |\
| |
| |
| |
| | |
tor-rtmock: Introduce MockTimeCore
See merge request tpo/core/arti!2052
|
| | |
| |
| |
| |
| | |
This was incorrect usage, as pointed out in
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2052#note_3012727
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It bothered me that when I added a `MockCoarseTimeProvider` to the
mock time providers, I had to manually grep to check that there
weren't places the time was updated where I ought to also update the
coarse time.
Prove that the code is right by hiding all the times together in a
struct that prevents un-synchronised updates.
This is part 1, where we move the fields from simple_time::State to
the new struct.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
We're going to put more in here.
(Yes, I know we just invented this...)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
tor-netdir: Fix broken links in NetParameters docs.
See merge request tpo/core/arti!2054
|
| | | |
| | |
| | |
| | | |
Spotted in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2053#note_3012632
|
| |/ /
| |
| |
| |
| | |
Instead, link to documentation, and give the warning about their
security.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-netdir: Add the vanguard params to NetParameters.
See merge request tpo/core/arti!2053
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
We'll need this to convert the `vanguard_enabled` and
`vanguard_hs_service` net params to a `VanguardMode.
|
| | |/
| |
| |
| |
| |
| | |
See also torspec!258
Part of #1272
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
With this patch, it holds only a reference to `&reactor.hops`,
which greatly simplifies the reactor code's fight with the
borrow checker.
I've left some TODO comments about future directions here.
|
| | |
| |
| |
| | |
(Doing this to prevent us having two structs with the same name.)
|
| | |
| |
| |
| | |
Closes #1124.
|
| | |
| |
| |
| |
| |
| |
| | |
Based on designs in #1124.
Note that there is a TODO here about a hack I had to do to appease
the borrow checker.
|
| | |
| |
| |
| |
| | |
We'll use this as an argument for the callback that checks stream
requests to make sure they're permitted.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
We want to keep an accurate count of the number of open streams, so
we have to stop exposing `&mut StreamEnt` outside of the streammap
module.
|
| | |
| |
| |
| |
| |
| |
| | |
This is the first part of a refactoring that will let us keep code
from the outside of `streammap` from changing a stream from one
state to another. And we need to do _that_ so that StreamMap can
count how many open streams it has.
|
| |\ \
| |/
|/|
| |
| | |
Refactor the logic for constructing crypt layers.
See merge request tpo/core/arti!2048
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The key insights here are:
- That relay cell format and crypto protocols aren't orthogonal:
Once we have GCO, it will require V1.
- That we only need the actual functions for layer construction to
be generic; we don't need to proliferate generic parameters
everywhere.
- That the circuit::handshake module already does most of what we
want.
|
| | |
| |
| |
| |
| | |
Modules with the same name as external crates don't work well with our
MSRV.
|
| | |
| |
| |
| |
| | |
Modules with the same name as external crates don't work well with our
MSRV.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
We must also impl CoarseTimeProvider for mocked runtimes.
|
| | | |
|
| | |
| |
| |
| | |
This reduces duplication a little.
|
| | |
| |
| |
| | |
Now all our non-mock runtime types impl CoarseTimeProvider.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
In all the uses in-crate, this is just a RealCoarseTimeProvider.
Now all the compound runtimes impl CoarseTimeProvider.
|
| | | |
|
| | | |
|
| | | |
|