| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
rpc-connect-point: Decline (not abort) on more invalid address formats.
Closes #2303
See merge request tpo/core/arti!3553
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we see an address schema we don't recognize, we're supposed to
_decline_ the connect point rather than aborting.
Closes #2303. See discussion at #1844.
Additionally, we tolerate more kinds of invalid address, in order to
permit future planned extensions.
|
| |\ \
| | |
| | |
| | |
| | | |
ci: always run pages job
See merge request tpo/core/arti!3549
|
| | | |
| | |
| | |
| | |
| | | |
it doesn't depend on anything else in the pipeline, so avoid skipping it
when other jobs fail
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow listening on port "auto", and reporting bound ports via a JSON file
Closes #1758
See merge request tpo/core/arti!3548
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was a little funny, since the other storage elements are
declared in tor-client. Fortunately, our stacked configuration
logic handles this fine.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This allows applications to find out where arti is listening when
arti has been configured to listen with the port "auto".
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, the proxy and dns modules only had "be a proxy"
functions that ran forever. Now they have functions that bind to
listeners and return a separate "be a proxy" future that runs
forever.
This lets us simplify some kludges in subcommands::proxy. More
importantly, it will let us return the bound-to ports so that
subcommands::proxy can write them to disk.
This is a break in experimental-apis, which does not require a
semver change.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
These are a nicer syntax than using port "0" explicitly.
|
| | | | |
| | | |
| | | |
| | | | |
Nothing actually uses it any more, which is good.
|
| | |/ /
| | |
| | |
| | |
| | | |
Have the part of them that does the "no multiple addresses" work
be common, so that we can simplify how they actually behave.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
shadow CI: disable stallouts for onion clients
See merge request tpo/core/arti!3529
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
tgen aborts a stream and starts the next one when the "stallout" timeout
is reached. In some cases the arti (or tor) client just needs a bit more
time to establish a connection to the hidden service.
A potential downside is that if a single stream "stalls" forever without
an explicit error, tgen will never give up on it, and thus never try any
more streams. We can worry about that if and when we see it though; and
it would indicate a likely bug since the known clients and servers in
this test shouldn't stall indefinitely in this way.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
arti,arti-relay: Change info-level keystore path msg to debug
See merge request tpo/core/arti!3546
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
build website for and deploy to static component
Closes tpo/tpa/team#42288
See merge request tpo/core/arti!3547
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
this uses the static-shim-deploy template to deploy the arti website to
arti.torproject.org, and tweaks the docusaurus baseUrl accordingly
it requires a STATIC_GITLAB_SHIM_SSH_PRIVATE_KEY CI variable which is
set up in project settings and contains the private key which allows
deployment of assets to static component web hosts
it also deploys a "_redirects" file to gitlab pages to ensure that the
old URLs are redirected
as previously, the website build and deployment jobs are only run in
(nightly) scheduled pipelines
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
ci: Keep doc artifacts
See merge request tpo/core/arti!3537
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Because Rust 1.91.0 makes it economically unfeasiable to run `cargo doc`
oneselves, it might wise to keep it as an artifact in `rust-dev-recent`
and `rust-nightly`, which generate the docs anyways, so we can keep us
away from having to run the expensive command when reviewing (larger)
changes to documentation.
For now, these artifacts will expire within a week.
Maybe this should get discussed, because on my local machine, they are
over 2GB large?
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
doc: Mention `experimental` feature in Semver.md
See merge request tpo/core/arti!3545
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The `experimental` feature flags are not explicitly mentioned anywhere
in the `doc/Semver.md` file.
This commit changes that by adding a paragraph documenting the status
quo, namely that functionalities gated behind an opt-in experimental
flag may break despite an unchanged major version number.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti: Remove 'rustls/tls12' feature
See merge request tpo/core/arti!3540
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We don't rely on this within the arti crate, and tor-rtcompat already
sets this. It's confusing to have it here as well. If the arti ecosystem
requires this, it should be enabled on the lower level crates (like it
already is in tor-rtcompat) so that arti-client users get it too.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
proto: Remove client specific channel circuit message
See merge request tpo/core/arti!3536
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
With a protocol violation, we have to immediately deal with such event
before emitting anything on the wire.
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This mirrors also the relay reactor. We've introduced the ProtoViolation
into a previous commit which is not an action but rather an "event" that
happened on a circuit.
And so, better semantic. No behavior change.
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Because of https://gitlab.torproject.org/tpo/core/torspec/-/issues/385
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Same as the client reactor, a message outside of our restricted set
leads to a reactor shutdown.
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Move the client specific unit tests into the client module.
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commit removes the CircuitRx* based solely on the client circuit
message and moves it into the top level of the crate so all reactors can
use them.
The client reactor then upon receiving the message, it converts the
AnyChanMsg into a ClientCircChanMsg. On error, this leads to a shutdown
of the entire reactor due to a fatal error.
In order to pull this off, we added a CircuitAction::Shutdown that is
handled as a priority.
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This follows the move of the client specific object.
Signed-off-by: David Goulet <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Next commit will also move the Relay specific set into the relay module.
These two sets are becoming specific to the reactor as the circuit
reactor communication channel will use AnyChanMsg instead.
Signed-off-by: David Goulet <[email protected]>
|
| |/ / / / /
| | | | |
| | | | |
| | | | | |
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti-relay: Install default ring crypto provider
See merge request tpo/core/arti!3539
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is what arti uses, and fixes the warning:
```text
WARN tor_rtcompat::impls::rustls: Creating a RustlsRuntime, but no CryptoProvider is installed. The application should call CryptoProvider::install_default()
```
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-netdoc: derive-based netdoc encoder
See merge request tpo/core/arti!3535
|
| | | | | | | |
|
| | | | | | | |
|
