| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Part of #872: Now that const generics are in, we have better ways to
express converting slices into array-references.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Incomplete branch to implement an RPC session registry and link SOCKS streams to RPC
Closes #863
See merge request tpo/core/arti!1208
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The actual decoding here is just a placeholder. The important part
is that we can get either a (SessionId, StreamId) tuple out of the
request, or we treat it as part of an isolation token.
This commit has a few TODOs for additional things that we'll need
in order to build out our design.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
This enables some small simplifications.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
It will use this to find which TorClient to use when opening a
stream.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These identifiers are actually only "global" with respect to a given
`RpcMgr`, but they should not be forgeable or reusable across RpcMgr
objects. We're going to use them so that we have a kind of identifier
for `TorClient`s that we can expose to SOCKS.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
We're going to use this to implement arti#863, which requires that
some RPC objects be globally nameable.
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-circmgr: send_control_message: Furrher docs changes
See merge request tpo/core/arti!1219
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1218#note_2908119
|
| | | | | |
|
| |\| | |
| |_|/
|/| |
| | |
| | | |
tor-circmgr: send_control_message: Clarify some corner cases
See merge request tpo/core/arti!1218
|
| | | |
| | |
| | |
| | |
| | |
| | | |
I am hoping we can merge this as a "TODO (Diziet)", even though I
think it may be controversial. Ie merging this doesn't represent a
decision to do as I suggest.
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also, no longer talk about handlers being "installed". That's not
something that's exposed by this API.
And, say that `send_control_message` can be called again only
after *`send_control_message`* returns, not when `handle_msg` has
returned `UinstallHandler`. IMO this makes more sense.
Explain that we can't maintain a continuous watch while holding a
conversation with the peer. (This is surely an API bug.)
|
| |\ \
| | |
| | |
| | |
| | | |
maint/cargo-audit: Ignore RUSTSEC-2023-0040 (the users crate is unmaintained)
See merge request tpo/core/arti!1217
|
| |/ /
| |
| |
| | |
Signed-off-by: Gabriela Moldovan <[email protected]>
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Bump crate versions in preparation for v1.1.5 release.
See merge request tpo/core/arti!1211
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Generated with the following commands:
```
cargo set-version --bump minor -p tor-cell
cargo set-version --bump minor -p tor-linkspec
cargo set-version --bump minor -p tor-proto
cargo set-version --bump minor -p tor-netdoc
cargo set-version --bump minor -p tor-circmgr
cargo set-version --bump patch -p tor-cert
cargo set-version --bump patch -p tor-basic-utils
cargo set-version --bump patch -p tor-rpcbase
cargo set-version --bump patch -p tor-llcrypto
cargo set-version --bump patch -p tor-hscrypto
cargo set-version --bump patch -p tor-checkable
cargo set-version --bump patch -p tor-async-utils
cargo set-version --bump patch -p caret
cargo set-version --bump patch -p fs-mistrust
cargo set-version --bump patch -p safelog
cargo set-version --bump patch -p retry-error
cargo set-version --bump patch -p tor-error
cargo set-version --bump patch -p tor-config
cargo set-version --bump patch -p tor-events
cargo set-version --bump patch -p tor-units
cargo set-version --bump patch -p tor-rtcompat
cargo set-version --bump patch -p tor-rtmock
cargo set-version --bump patch -p tor-protover
cargo set-version --bump patch -p tor-bytes
cargo set-version --bump patch -p tor-socksproto
cargo set-version --bump patch -p tor-consdiff
cargo set-version --bump patch -p tor-netdir
cargo set-version --bump patch -p tor-congestion
cargo set-version --bump patch -p tor-persist
cargo set-version --bump patch -p tor-chanmgr
cargo set-version --bump patch -p tor-ptmgr
cargo set-version --bump patch -p tor-guardmgr
cargo set-version --bump patch -p tor-dirclient
cargo set-version --bump patch -p tor-dirmgr
cargo set-version --bump patch -p tor-hsclient
cargo set-version --bump patch -p tor-hsservice
cargo set-version --bump patch -p arti-client
cargo set-version --bump patch -p arti-rpcserver
cargo set-version --bump patch -p arti-config
cargo set-version --bump patch -p arti-hyper
cargo set-version --bump patch -p arti
cargo set-version --bump patch -p arti-bench
cargo set-version --bump patch -p arti-testing
```
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
changelog: mention fallback list update.
See merge request tpo/core/arti!1212
|
| |/ / / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
fallbackdir: Update list generated on June 01, 2023
See merge request tpo/core/arti!1210
|
| |/ /
| |
| |
| | |
Signed-off-by: Tor CI Release <[email protected]>
|
| |\ \
| | |
| | |
| | |
| | | |
changelog: add links for 1.1.5 changelog
See merge request tpo/core/arti!1209
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Draft a changelog for 1.1.5
See merge request tpo/core/arti!1207
|
| | | | |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
New script to run cargo-semver-checks with appropriate options.
See merge request tpo/core/arti!1206
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The options are rather complicated; because we do not want to
subject our experimental features to semver, we need to run generate
JSON rustdoc on our own and then pass that JSON to
cargo-semver-checks. This in turn requires us to use the same
options that cargo-semver-checks uses, including "RUSTC_BOOTSTRAP".
I've left some TODOs here in places where we will likely want to
improve our code in the future.
See #711.
|
| |\ \
| | |
| | |
| | |
| | | |
Run fixup-features script and resolve its complaints.
See merge request tpo/core/arti!1205
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| | |
Run "cargo update" in preparation for Thursday release.
See merge request tpo/core/arti!1204
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
Experimental new stream-ctrl feature
Closes #847
See merge request tpo/core/arti!1198
|
| | | |
|
| | |
| |
| |
| | |
There are some weaknesses and problems here; see TODO notes.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The idea here is that we want to make DataStream visible to the
RPC system without requiring that the RPC session hold the
DataStream itself (or the Reader, or the Writer). We could solve
this problem by making _all_ the state in the DataStream shared,
but that would introduce unnecessary extra locking in our critical
path.
Instead we're creating the notion of a "control handle" that lets
you manage and observe a stream without actually owning the stream.
Right now the only supported functionality is asking for the
stream's circuit.
Part of #847
|
| | |
| |
| |
| |
| | |
(It doesn't do anything yet. It may eventually become always-on.
But for now let's make this API optional. Part of #847)
|
| | | |
|