Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
5. TLS, identity and DNS
lib/http/src/tls_context.cpp configures a server context, checks the leaf/key
pair and enforces the selected TLS minimum. Cloud operation is HTTPS-only.
Native names and Azure-emulation names use separate listeners/certificates;
this does not implement general SNI certificate selection or hot certificate
reload on one listener. Server configuration errors fail startup rather than
falling back to plaintext.
There are separate constrained development, Azure-emulation and engine trust domains. The telemetry tools have their own local CA. CA signing keys are not mounted into ordinary server/client containers. QHQ and SDK clients verify certificate chains and hostnames. The engine supervisor additionally serves a signed CRL for native clients that require revocation checking.
Identity issues RS256 client-credentials tokens with service audiences and a one-hour lifetime. Its signing key is process-local, so cloud restart invalidates existing tokens. Audience checks separate management, storage, vault and monitoring calls. Bootstrap credentials retain administrator access. New service principals, managed identities and interactive users require scoped ARM/Service Bus roles; other data planes deny them until their role families are implemented. See the identity contract (source checkout required).
The DNS module collects provider-published names and custom records, generates zones/CoreDNS configuration, and observes the Azure-emulation switch. Native engine records use actual instance IPs. Persisted DNS serials remain monotonic across rapid updates/restart; resetting a serial to wall time could otherwise leave CoreDNS serving old state.
References: certificate infrastructure (source checkout required), Azure emulation (source checkout required), DNS (source checkout required), engine TLS/CRL (source checkout required) and the user trust guide.