mirrors/arti.git/crates/tor-hsservice/src/lib.rs, branch arti-v1.3.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.02024-10-17T10:25:33ZDisable a lot of dead code warnings (fmt)2024-10-17T10:25:33ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-17T10:25:20Zurn:sha1:731adee5ad984dd1226eb917b20bb1380065aa09Disable a lot of dead code warnings2024-10-17T10:25:24ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-16T14:27:16Zurn:sha1:107ad43db8b7d619f5076ab37c92dcce7a25c223
Now
cargo check --workspace --no-default-features --all-targets
cargo build -p arti --no-default-features --features=memquota,tokio,native-tls
are both clean.
Introduce mpsc_channel_no_memquota and use it in the places it's wanted2024-10-15T10:52:34ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-09T18:00:03Zurn:sha1:fe219904a9c70fc1c9079a88e9ecefb151ac47e4
These are the call sites where using this fucntion is correct.
(Outside tor-rtmock, which we'll do separately.)
tor-hsservice: Move HsNickname to tor-persist.2024-10-08T13:21:13ZGabriela Moldovangabi@torproject.org2024-09-26T12:13:18Zurn:sha1:c744120a6709810bf89458485b8439ebabd02451
We are about to need this in `tor-keymgr`, where we're about to add a
config for C Tor service keystores (the C Tor keystore config will have
an associated `HsNickname` that specifies which of the arti hidden
services it's supposed to be used with).
tor-hsservice: Update docs to reflect KeystoreSelector renaming.2024-09-23T13:27:06ZGabriela Moldovangabi@torproject.org2024-09-23T13:27:06Zurn:sha1:06c3e82e06938df01addfc7ac0cd471ad88060dctor-keymgr: Rename the primary keystore for clarity.2024-09-23T13:17:49ZGabriela Moldovangabi@torproject.org2024-09-20T10:20:33Zurn:sha1:80095da1aa47978cdba26c2b3d254a99c075cf53
Previously, arti's primary keystore was referred to as its "default"
keystore. However, "default" is inaccurate here: there is no way to
meaningfully override this "default" (the "default" store acts as the
main keystore). Throughout the codebase, we query all keystores for keys
(including the secondary ones), but only ever write to the
default/primary keystore. This is OK for now, because it enables us to
have one mutable keystore, and multiple secondary, read-only stores.
tor-hsservice: Add API for generating the hsid for a service.2024-09-17T14:03:22ZGabriela Moldovangabi@torproject.org2024-09-16T16:24:06Zurn:sha1:e685301d445934a42936bbda4e6cab8032c06f74
This also reexports `HsId` from the `tor-hsservice` crate.
tor-hsservice: Make maybe_generate_hsid take a selector (fmt).2024-09-17T14:03:22ZGabriela Moldovangabi@torproject.org2024-09-16T16:58:39Zurn:sha1:6de8952647a9d6277160612355d3d04bbbff2848tor-hsservice: Make maybe_generate_hsid take a selector.2024-09-17T14:03:22ZGabriela Moldovangabi@torproject.org2024-09-16T16:19:34Zurn:sha1:d4fb55f5af4664c1c2858e949fda140e1d15a276
We will soon add a new `OnionService` function for generating an HsId
for the service without launching it (#1621).
This new API will be implemented using `maybe_generate_hsid`, which will
need to take the user-provided keystore selector as an argument.
(the selector exists for future-proofing reasons; we're not yet exposing
it in the CLI, but it will be part of the new `OnionService` API)
tor-hsservice: Do not generate the HsId until the service is launched.2024-09-17T09:25:26ZGabriela Moldovangabi@torproject.org2024-09-16T14:31:46Zurn:sha1:eb38589fcf186e91008b35d98f53d44799578a1c
This defers generating an HsId until `OnionService::launch`, enabling us
to use APIs like `OnionService::onion_name` to e.g. check for the
existence of an HsId (previously, you couldn't do that because creating
an `OnionService` would auto-generate the `HsId`).