mirror of
https://github.com/hanzoai/gateway.git
synced 2026-10-30 15:04:44 +00:00
Minting is issuing authority. IAM signs the token, and the signature is where the authority is created. This edge VERIFIES a token and restates what it proved as headers, so a transport that cannot carry a token can read the same decision. Calling both operations "mint" put the issuer's job and the edge's under one word, and a word that covers two operations stops distinguishing them — a reader who thinks the edge mints reads it as a second issuer. So every use of `mint` for writing or stripping identity HEADERS becomes `write`, which is already the leaf's own word (hanzoai/authz: "strips every identity header on ingress and rewrites it from verified claims"). The identifiers follow: SetGatewayMinted/AssertGatewayMinted become SetGatewayWritten/AssertGatewayWritten, mintIdentity becomes writeIdentity, and waitlistMintedHeaders becomes waitlistHeaders — they are simply the guard's own response headers, and the adjective added nothing but the wrong verb. `mint` stays where it is correct: IAM issuing a token, a sign-in issuing a session cookie, commerce creating balance, and "the app the token was minted through". Two doc citations named symbols the migration removed and are re-pointed at the live ones: edge.Mint to edge.Render, gatewayMintedIdentityHeaders to authz.Headers. Co-authored-by: Hanzo Dev <[email protected]>
834 B
834 B
Security Policy
Reporting a vulnerability
Email [email protected] with details. Encrypt with our PGP key (fingerprint TBD).
We respond within 48 hours. Critical issues receive same-day acknowledgment.
Scope
This policy covers code in this repository. For the broader Hanzo platform threat model, see hanzoai/HIPs.
Sandbox boundary
gateway is the only Hanzo service that writes identity headers from JWTs — every client-supplied X-User-*, X-Org-Id, and X-Roles header is stripped unconditionally before processing. JWT validation runs against the Hanzo IAM JWKS endpoint, and rate limiting / circuit breakers isolate failures so a misbehaving client or downstream cannot affect other tenants.
For runtime sandbox guarantees, see HIP-0105 (in-process extension runtimes).