mirrors/arti.git/crates/tor-hsservice/src/lib.rs, branch arti-v1.9.0

Merge branch 'disable-hidden-service' into 'main'

2025-11-12T16:08:04Z

arti/arti-client/tor-hsservice: Support disabling onion services in the config Closes #2133 See merge request tpo/core/arti!3253

Fix name of clippy lint to unchecked_time_subtraction (2)

2025-11-06T11:28:22Z

Run maint/add_warning

arti(-client)/tor-hsservice: return None for disabled service

2025-10-16T22:48:46Z

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 <3924-hashcatHitman@gitlab.torproject.org>

arti/tor-hsservice: don't warn on autostart

2025-10-16T22:48:46Z

The "enabled" config option is back to using a regular `bool`. When unset, it defaults to true, and the service runs as if it had been set. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

arti/tor-hsservice: warn on service autostart

2025-10-16T22:48:46Z

The "enabled" config option now uses `tor_config::BoolOrAuto`. When unset (which defaults to "Auto"), the service will run with a warning. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

tor-hsservice: add config to disable service

2025-10-16T22:48:45Z

Added the `enabled` field to the config options for hidden services. The default is `true`. If it is set to `false`, the service won't start. As of this specific commit, it's a hard error; it'll be checked again at an earlier stage where it won't be once the feature is ready. Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

Remove "doc_auto_cfg" incantation from all crates.

2025-09-29T19:30:03Z

This feature has been removed from nightly, in favor of doc_cfg.

hsservice: Remove misleading OnionService note.

2025-09-12T10:25:26Z

An `OnionService` represents a not-yet-running service. To launch it, you have to call `OnionService::launch()`, which consumes the `OnionService` and returns `RunningOnionService`, so the part of the docs saying that an `OnionService` "may or may not be running" was somewhat misleading.

hsservice: Say how a RunningOnionService is constructed.

2025-09-12T10:08:23Z

This adds some extra docs to `RunningOnionService`. This also removes the TODO about #1228, because that ticket was closed in !1945.

hsservice: Remove an already-addressed TODO.

2025-09-12T10:04:10Z

In #1247 we decided to stick with the current names.