| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
Typos found with codespell
|
| |
|
|
|
|
|
|
|
|
| |
There is no longer a hard error anywhere for trying to launch a service
which is disabled in the config. Instead, it always means returning
`Ok(None)`.
The axum and hyper examples were updated again as a consequence.
Signed-off-by: hashcatHitman <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
| |
When a service is disabled in the config, `arti::onion_proxy::Proxy`
handles it gracefully, and
`arti_client::client::TorClient::launch_onion_service_with_hsid` and
`arti_client::client::TorClient::launch_onion_service` both hard error.
The axum and hyper examples were updated again as a consequence.
Signed-off-by: hashcatHitman <[email protected]>
|
| |
|
|
|
|
|
|
|
| |
Hidden services disabled in the config are now handled more gracefully
by arti/arti-client, before the hard error occurs.
The axum and hyper examples were updated as a consequence.
Signed-off-by: hashcatHitman <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The `stream` module is client-specific, for the most part, so I am
moving it under `client`. Later on, we will factor out the parts that
can be shared with the relay implementation.
Note: this is a breaking change as the deleted `stream` module was
`pub`. We could've kept the module and reexported from it the public
types from `tor_proto::client::stream`, but I think it's better to have
this `client` namespacing, because it makes the separation between the
client and relay parts clearer.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Conflicts:
examples/hyper/hyper-http-client-example/Cargo.toml
examples/hyper/hyper-http-hs-example/Cargo.toml
In both cases, just the change of edition, which I have applied to
examples/hyper-examples/Cargo.toml
instead.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
# Conflicts:
# examples/hyper-examples/src/bin/hyper-http-hs-example.rs
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Previous comment was not clear. `is_fully_reachable` only gives false negatives, not false positives.
|
| |
|
|
| |
We removed the while loop.
|
| | |
|
| |
|
|
|
|
|
|
| |
The reason we prefer `rustls` in this case is because `rustls` provides
better portability then `native-tls` due to not being dependent on the system.
We have to explicitely set the root_cert because `rustls` does not use the
system CA Certs to remain portable.
|
| | |
|
| | |
|
| |
|
|
| |
We will make a separate library for this.
|
| | |
|
| |
|
|
|
|
|
|
| |
This example previously remained stuck in the while loop without any output, seeming as if this example is not working.
This because the method `is_fully_reachable` is no guarantee for the actual status of the onion service. It might return false while the service is actually reachable.
We added a timeout to not remain stuck in the loop.
|
|
|
This directory had to be renamed because otherwise it would cause conflicts with the actual hyper crate in the CI pipeline.
|
