Expand description
Typed RPC dispatch labels — the focused #1499 boot-labeling slice.
The mandatory RPC dispatch PEP (hyprstream_rpc::auth::mac::dispatch_pep)
evaluates a typed declared (service, leaf/method) object identity plus
a deliberate service subject clearance. This module supplies both, keyed
on the dispatch plane’s own coordinates:
DispatchMethodId— the typed object identity: the canonical service name plus the canonical request-union discriminant (the leaf/method), decoded once from the verified payload by the dispatch pipeline. It is never a VFS path, and bare service domains are never routed through the VFS object-label adapter (CompositeObjectLabelResolver’sRpcObjectLabelResolverimpl now serves the VFS plane only).ServiceSubjectClearance— the deliberate clearance a declared bootstrap service holds as a caller, the dispatch-plane seed of the v16ServiceEnrollmentManifestclearance. The assurance axis is clamped by the cryptographically verified key material at evaluation time, so the declaration can never outrun what the envelope signature proved.
§Deny-by-default
There is no wildcard, catch-all, prefix rule, or permissive default. An
unknown service, an unknown leaf on a known service, a bare/VFS-shaped
alias ("/srv/policy", "srv/policy"), and a call whose payload carries
no canonical method identity all resolve to None ⇒ UnlabeledObject ⇒
deny before handler entry. A caller with no declared service clearance —
including an anonymous caller, for whom the activation floor would
otherwise suffice against a floor-labeled row — denies NoClearance. The
permit of a declared bootstrap call is therefore justified by the
declared pair (typed object + deliberate clearance), never by a
fabricated anonymous/public clearance.
§Relationship to #1507 (v16)
This is the smallest deny-by-default representation the production PEP can
evaluate today. #1507 replaces the hand-maintained tables with the
generated full-method inventory (transitional/target label columns, scope
and signature policy) without changing the PEP contract: typed (service, leaf) resolution, declared subject clearance, activation-gated selection,
and intrinsic lattice dominance all stay. Object labels here are
deliberately the lattice floor (SecurityLabel::bottom()): the bootstrap
identity-lifecycle leaves precede identity standing and must remain
reachable under the permanent narrow-to-floor incident control
(FloorOnly); every raising above the floor is #1507’s reviewed
transitional/target column work, not this slice.
Modules§
- discovery_
methods - Canonical
DiscoveryRequestunion discriminants used by native startup. - inference_
methods - Canonical
InferenceRequestunion discriminants. - policy_
methods - Canonical
PolicyRequestunion discriminants (the leaf/method axis ofDispatchMethodId).
Structs§
- Declared
Dispatch Pep - The production dispatch PEP over the declared table.
- Declared
Dispatch Table - The declared dispatch table: a closed, deny-by-default set of typed
(service, leaf/method)object labels plus the deliberate per-service subject clearances. Consumed byDeclaredDispatchPep; replaceable by #1507’s generated inventory without changing the PEP contract. - Dispatch
Method Id - Typed dispatch object identity: canonical service name + canonical request-union discriminant. Never a VFS path; never interpreted by another plane’s resolver.
- Dispatch
Method Policy - One declared
(service, leaf/method)policy row: the typed object label for exactly one RPC method on exactly one service. - Service
Subject Clearance - The deliberate MAC clearance a declared service holds as a dispatch
caller — the dispatch-plane seed of the v16
ServiceEnrollmentManifestservice clearance.
Constants§
- BOOTSTRAP_
SERVICE_ CLEARANCE - Clearance for the narrow local Policy bootstrap authority and classical test fixtures. Enrolled native services use the hybrid ceiling below. The assurance axis is a ceiling, not a grant — evaluation clamps it to the cryptographically verified key material (#548), so a caller whose envelope proved less derives less.
- HYBRID_
SERVICE_ CLEARANCE - Service subject clearance for the hybrid-enrolled runtime services whose
RPC surfaces are schema-declared
internal:pq-hybrid(model,oai,inference). Identical in value toOAUTH_ISSUANCE_LABELandINFERENCE_METHOD_LABEL; the distinct names keep each declaration’s review intent legible. - INFERENCE_
METHOD_ LABEL - Schema-declared label of every
InferenceRequestmember. - OAUTH_
ISSUANCE_ LABEL - Schema-declared label of
PolicyRequest.issueToken. - SERVICE_
SUBJECT_ PREFIX - Subject-name prefix of a verified service identity (
service:{name}).