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§
- Observed
Peer - What the daemon learned from the kernel about the process that opened the route, read once when its connection was accepted.
- Operator
App - The daemon’s statement that the route was opened over a connection it recognised, when the connection was made, as a verified operator app.
- Route
Bind Peer - The
route.bindkeys carried besideModuleControlRequest::RouteBind.
Enums§
- Observed
Peer Status - 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.providesasks the daemon forRouteBindPeer::observed_peeron everyroute.bind. - OPERATOR_
APP_ CAPABILITY - Declaring this in
capabilities.providesasks the daemon forRouteBindPeer::operator_appon aroute.bindwhose route was opened by a recognised operator app.
Functions§
- encode_
route_ bind - Encodes a
route.bindbody withpeer’s keys after the bind’s own keys.