| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| | |
release: Bump versions.
See merge request tpo/core/arti!2981
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
```
cargo set-version --bump patch -p arti
```
|
| | |
| |
| |
| |
| |
| |
| |
| | |
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.30.0
done
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
```
Of these, only hashx and fs-mistrust have changed, as per:
```
./maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
```
So these were updated with:
```
./maint/bump_nodep hashx fs-mistrust
```
|
| |/
|
|
| |
Done via `./maint/update-release-date`.
|
| |\
| |
| |
| |
| | |
Fix typos
See merge request tpo/core/arti!2961
|
| | |
| |
| |
| |
| | |
The backspace character leads to funny results, depending on tool
or terminal used to show content of the file.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-cell: Add `UnparsedRelayMsg::data_len`
See merge request tpo/core/arti!2976
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
maint: Update semver.md files from semver-checks
See merge request tpo/core/arti!2977
|
| | | | | |
|
| | | | | |
|
| | |/ / |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
cargo run -p fixup-features -- --exclude examples/ --exclude maint/ Cargo.toml
The following features in arti-ureq were manually added to full or
marked non-additive:
* rustls
* native-tls
* tokio
* async-std
|
| | |
| |
| |
| |
| |
| | |
Now that choose_multiple_weighted can once more return
fewer items than requested, we should warn when it does so,
to be consistent with our other cases of warning about #1907.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Rand 0.9.1 reverted the changes that caused #1903,
in https://github.com/rust-random/rand/pull/1623.
This broke our test that made sure that rand wasn't going to change
their behavior _again_ :)
|
| | |
| |
| |
| |
| | |
(This is going to be a _requirement_,
since rand 0.9.1 has a behavioral change from 0.9.0)
|
| | |
| |
| |
| |
| | |
I updated everything except rand, because the new version of rand
interacts with #1903, thus requiring more care.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Updates:
* hashlink 0.9.1 -> 0.10.0
* Updates hashbrown
* metrics-exporter-prometheus 0.16.2 -> 0.17.0
* Bumps deps
* Minor API change
Not updated:
* rusqlite, due to MSRV incompatibility
* educe (#1257)
* hickroy-proto (https://github.com/hickory-dns/hickory-dns/issues/2956)
|
| | |
| |
| |
| | |
(The u8 code was written before RelayCellFormat::V1 was introduced.)
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
See discussion at torspec#328: it's important that our
SENDME authentication tag always be taken based on the
_encrypted_ cell.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This provides all the operations from proposal 359,
along with the necessary integration and unit tests to make sure
that they are behaving properly.
Closes #1943
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
These are a tweakable block cipher, and a pseudorandom byte stream.
This commit includes test vectors, which were generated from the
Python reference implementation and confirmed with a less optimized
Rust implementation.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
(We'll need these tags both to implement authenticated SENDMES
at the relay side, and also to make sure that cgo is generating them
correctly.)
|
| | |
| |
| |
| |
| |
| | |
CGO will need this argument so that it can authenticate
the command as part of its crypto operations.
(Trying to meddle with RELAY vs RELAY_EARLY will no longer work!)
|
| | |
| |
| |
| |
| |
| | |
It seems very likely that, as with client crypto,
we'll want relay crypto to separable into "forward" and "reverse"
objects, so that the two can be used more or less independently.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes the behavior of "originate" match the behavior of
OutboundClientLayer::originate_for, which creates the message
_and_ encrypts it. This will be necessary for CGO, where
"originate" and "encrypt" are not easily separated operations.
(Nothing uses this trait yet, since relay circuits aren't yet a thing,
so it's a good time to get it right.)
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Since we're about to have a second kind of relay cell crypto,
it makes sense to move this module.
This change is pure code movement.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Log conventions
Closes #1906
See merge request tpo/core/arti!2966
|
| | |/ |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
This was missed in commits ccb65961 and eeda643f. While
`params.ccontrol.is_enabled()` should always be false because of those
earlier commits which ensure we don't enable congestion control, we were
missing the defense-in-depth conditions here that would alert us if we
accidentally did enable congestion control.
|
| |\
| |
| |
| |
| |
| |
| | |
Implement congestion control handshake negotiation
Closes #1817
See merge request tpo/core/arti!2932
|
| | |
| |
| |
| |
| | |
This means that even with the "flowctl-cc" feature enabled, we shouldn't
try to negotiate congestion control.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Congestion control is not completely working correctly, and is not fully
implemented (XON/XOFF). This commit adds a new experimental "flowctl-cc"
feature to enable the congestion control extension during the ntor-v3
handshake.
|
| | | |
|
| | | |
|
