Expand description
Administrative RPC functionality.
In general, RPC function is βadministrativeβ, and requires superuser access, whenever it can affect other applications.
This is not a perfect sandbox: applications can always interfere with one anotherβs traffic by consuming resources (like bandwidth or CPU) in a way that introduces side channels.
Re-exportsΒ§
use arti_client::TorClient;πuse arti_client::rpc::ClientStatusInfo;πuse derive_deftly::Deftly;πuse futures::FutureExt as _;πuse futures::SinkExt as _;πuse futures::StreamExt as _;πuse futures::select_biased;πuse std::sync::Arc;πuse tor_rpcbase as rpc;πuse tor_rtcompat::Runtime;πuse crate::reload_cfg::CfgMgr;πuse crate::reload_cfg::LaunchableTorClient;π
StructsΒ§
- Bootstrap
Client π - Tell a client to connect to the network and bootstrap itself.
- Enter
Dormant πMode - Enter βdormant modeβ.
- RpcSuperuser π
- An object representing superuser access to Arti over an RPC session.
FunctionsΒ§
- bootstrap_
client_ πon_ rpcsuperuser - Implementation for
BootstrapClientonRpcSuperuser. - enter_
dormant_ πmode_ on_ rpcsuperuser - Implementation for
EnterDormantModeonRpcSuperuser.