| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| |/
|
|
|
|
|
| |
This was disabled due to lack of vanguard support. Now that we support
vanguards, we should enable this by default.
Fixes: #1402
|
| |\
| |
| |
| |
| |
| |
| | |
Replace references to prop351 with socks-extensions.md
Closes #1629
See merge request tpo/core/arti!2492
|
| | |
| |
| |
| |
| |
| |
| | |
Now that the proposal is implemented and merged into the specs,
the proposal itself is only historical.
Closes #1629.
|
| |\ \
| | |
| | |
| | |
| | | |
Use {u64,usize}::div_ceil
See merge request tpo/core/arti!2473
|
| | | |
| | |
| | |
| | |
| | | |
Previously we had to avoid it, but now that our MSRV is above 1.73
we can use it with abandon.
|
| | | |
| | |
| | |
| | | |
Based on review from @opara.
|
| | |/
|/|
| |
| |
| |
| | |
Previous documentation was more-or-less meant for the Arti developer
only. This new documentation is intended for actual users of RPC
functionality. It's meant to be extracted with `maint/rpc-doc-tool`.
|
| |\ \
| | |
| | |
| | |
| | | |
Copy section on objectid/isolation restrictions from prop351.
See merge request tpo/core/arti!2474
|
| | |/
| |
| |
| |
| | |
Eventually it belongs in an RPC spec, but for now the relevant
discussion goes here.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
New tor-socksproto API
Closes #1627
See merge request tpo/core/arti!2436
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This restores the functionality of
socks users: detect closed sockets.
0c595818f713916d94b7b0e4062f953fad7c9799
which we reverted as part of rebasing this branch onto main.
|
| | | |
| | |
| | |
| | | |
This is neater, I think.
|
| | | |
| | |
| | |
| | | |
Fixes #1627 / TROVE-2024-010
|
| | | |
| | |
| | |
| | | |
No functional change.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This deduplicates some docs and eliminates the two wrapper functiosn
for `run_handshake`, which is now just `handshake`.
We're going to make other API breaks too, and this isn't going to be
the primary API, so we might as well do this.
Proper description of the semver breakage will come at the end when
it's all done.
|
| | | |
| | |
| | |
| | | |
This reverts commit 0c595818f713916d94b7b0e4062f953fad7c9799.
|
| | | |
| | |
| | |
| | | |
This reverts commit dceeb82f7d1154894ab9c7c607d68f8335bb9615.
|
| | |/
| |
| |
| |
| |
| | |
data"
This reverts commit 87e0109832559dec41a485b268579d58be0de278.
|
| |\ \
| |/
|/|
| |
| | |
Warn on nonlocal addresses in configuration, PT results
See merge request tpo/core/arti!2454
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Remove semver.md files from 1.2.8
See merge request tpo/core/arti!2467
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
arti: Silence unused_mut warning.
See merge request tpo/core/arti!2431
|
| | | |
| | |
| | |
| | | |
The `config` is only mutated if `onion-service-service` is enabled.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Generated with
```
cargo set-version --bump patchlevel -p arti
```
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Per our policy, every one of these gets a minor bump.
Generated with:
```
for crate in $(./maint/list_crates | grep '^\(tor\|arti\)-' ); do
cargo set-version --bump minor -p $crate;
done
```
(Note the use of `-` at the end end of the grep pattern to prevent
matching the `arti` crate.)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These crates are not in the tor/arti namespace,
but we have given them MSRV bumps:
```
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
```
We are counting this as a breaking change.
Since all of these crates are at 0.x.x,
we have indicated the breaking change with a minor version bump.
This commit was generated with the following script:
```
BUMPS="
oneshot-fused-workaround
slotmap-careful
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
test-temp-dir
retry-error
"
for crate in $BUMPS; do
cargo set-version --bump minor -p $crate;
done
```
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
arti: add an example for onion service "reject" option
See merge request tpo/core/arti!2458
|
| | | | |
| | | |
| | | |
| | | | |
There was previously no example here.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti: move 'relay' subcommand to 'subcommands::relay' module
See merge request tpo/core/arti!2455
|
| | | | | | |
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Upgrade MSRV to 1.77 , and rusqlite to 0.32.1
See merge request tpo/core/arti!2451
|
| | | |_|/
| |/| |
| | | |
| | | | |
This will allow us to upgrade to the latest version of rusqlite.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Upgrade dependencies in preparation for next week's releases.
See merge request tpo/core/arti!2450
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When calling copy_within, we want to copy the amount of data that
we're keeping; previously, we were copying an extra `action.drain`
bytes, which could have led to a panic.
Spotted by Opara.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Without this check, our socks code can enter an infinite loop
if a socket is closed at the wrong time.
Resolves TROVE-2024-011.
Fixes #1635.
|
| |\ \
| | |
| | |
| | |
| | | |
socks: Implement proposal 351.
See merge request tpo/core/arti!2401
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Introduce an enum, and use explicit `format_code @` syntax.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
(These streams would already be isolated by accident, since streams
with an RPC object are always on a client that's isolated from the
main client. But, as discussed on torspec!280, it's best to do this
sort of thing explicitly.)
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The current best source here is prop351,
and later will be socks-extensions.md.
The examples are now correct.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
See https://spec.torproject.org/proposals/351-socks-auth-extensions.html
This proposal changes the interpretation of SOCKS5
usernames/passwords to give a more principled and extensible way of
getting RPC IDs and isolation strings.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
arti SOCKS proxy: Tear down connections when client sends optimistic data
See merge request tpo/core/arti!2443
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We *do* want to support optimistic data, see
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2436#note_3081886
However, right now, Arti risks mis-framing bugs if clients do send
optimistic data, which would be quite serious.
Mitigates #1627 / TROVE-2024-010 by replacing the misframing bug with
connection failure.
It doesn't seem so easy to write a test case for this.
|