Skip to main content

Module superuser

Module superuser 

Source
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Β§

BootstrapClient πŸ”’
Tell a client to connect to the network and bootstrap itself.
EnterDormantMode πŸ”’
Enter β€œdormant mode”.
RpcSuperuser πŸ”’
An object representing superuser access to Arti over an RPC session.

FunctionsΒ§

bootstrap_client_on_rpcsuperuser πŸ”’
Implementation for BootstrapClient on RpcSuperuser.
enter_dormant_mode_on_rpcsuperuser πŸ”’
Implementation for EnterDormantMode on RpcSuperuser.