Skip to main content

Module peer

Module peer 

Source
Expand description

Daemon-observed facts about the process on the other end of a route’s opening connection, relayed to the target module on route.bind.

These keys sit outside the exhaustive ModuleControlRequest::RouteBind variant so that adding them changes no Rust construction site. A daemon encodes a bind with encode_route_bind, which appends them after the variant’s own keys; a module decodes the same body twice, once as ModuleControlRequest and once as RouteBindPeer.

Each key is sent only to a target declaring its capability in capabilities.provides, and a target declaring neither receives exactly the bytes it received before these keys existed.

Structs§

ObservedPeer
What the daemon learned from the kernel about the process that opened the route, read once when its connection was accepted.
OperatorApp
The daemon’s statement that the route was opened over a connection it recognised, when the connection was made, as a verified operator app.
RouteBindPeer
The route.bind keys carried beside ModuleControlRequest::RouteBind.

Enums§

ObservedPeerStatus
Whether the daemon could read the peer’s identity from the kernel when it accepted the connection.

Constants§

OBSERVED_PEER_CAPABILITY
Declaring this in capabilities.provides asks the daemon for RouteBindPeer::observed_peer on every route.bind.
OPERATOR_APP_CAPABILITY
Declaring this in capabilities.provides asks the daemon for RouteBindPeer::operator_app on a route.bind whose route was opened by a recognised operator app.

Functions§

encode_route_bind
Encodes a route.bind body with peer’s keys after the bind’s own keys.