Skip to main content

Module browser_provisioning

Module browser_provisioning 

Source
Expand description

Accepted-current browser/WebTransport recipient provisioning.

The wire document in this module is public discovery material, not an authority token. Production documents are projected by Discovery only from its opaque checkpoint-bound ResolvedService. Browser consumers validate the complete context and build per-resolution stores from the result; they never install the material in a process-global trust store.

Structs§

BrowserProvisioning
Opaque, fully validated provisioning snapshot used for dial/seal.
BrowserProvisioningDocument
JSON document returned by the production provisioning endpoint.
BrowserProvisioningMaterial
Raw public values used by the trusted server-side projection.
BrowserProvisioningRequest
Exact context requested by a browser consumer.
BrowserRequestBinding
Accepted-state evidence copied into the signed and HyKEM-sealed request. Dispatch verifies it against the live checkpoint source before handler work.
BrowserRequestTranscript
Authenticated browser-only transcript metadata exposed to the generated service dispatcher. The generated dispatcher independently decodes its request union and compares that schema discriminator with this commitment.

Enums§

BrowserCarrierProfile
Carrier policy selected before any browser dial.
BrowserRouteRole
Route role bound into the provisioning context.
BrowserTranscriptPolicy
Explicit dispatch profile for the inner extension. A browser extension is mandatory only on its browser carrier and is rejected as a misclassified payload on every other carrier.
BrowserTransportSecurity
Honest transport-security classification. This is kept separate from the application HyKEM requirement so a classical relay cannot raise assurance.

Constants§

BROWSER_PROVISIONING_VERSION
BROWSER_RPC_PATH
WebTransport CONNECT path whose accept boundary requires browser provisioning.
MAX_BROWSER_APPLICATION_BYTES
MAX_BROWSER_BINDING_BYTES
MAX_BROWSER_EXTENSION_BYTES
MAX_PROVISIONING_BYTES
MAX_PROVISIONING_LIFETIME_MS

Traits§

BrowserCurrentnessVerifier

Functions§

bind_request_payload
Place accepted-current evidence and the application request in one bounded, canonical transcript before the normal hybrid signature and request HyKEM seal are constructed.
canonical_method_discriminator
Independently decode the canonical top-level Cap’n Proto request-union discriminator from a fully decoded request. Generated service dispatch uses this value; the browser extension only carries the client-side commitment.
recover_request_payload
Recover authenticated evidence after signature verification and HyKEM open. Canonical reserialization rejects alternate encodings as well as Serde’s unknown/duplicate-field rejection.