Skip to main content

Module tls

Module tls 

Source
Expand description

DNS-01 wildcard certificate issuance for the account zone (epic #1158, ticket #1162 / A3).

rustls-acme, which the crate already uses for HTTP-01/TLS-ALPN-01, only fulfills TLS-ALPN-01 challenges — its AcmeState cannot perform DNS-01, and DNS-01 is the only validation method public CAs accept for a wildcard identifier (*.<apex>). Wildcards cannot use HTTP-01.

hyprstream therefore defines the issuance path itself, behind a trait: WildcardCertIssuer owns the ACME DNS-01 dance (order → authorization → publish TXT via the DnsProvider seam → poll → finalize), and returns a DER-encoded cert+key. The concrete ACME-directory client and the DNS backend are both product-layer concerns above this crate — hyprstream must not depend on a specific DNS server (the self-hoster rule).

What hyprstream does own here is:

  • the shape of the request (zone, zone-scoped credential, ACME directory),
  • the sane-degrade when no zone is configured (clear error, no panic, no synthesized default),
  • the renewal + expiry-alarm plumbing (see super::renewal).

Converting an IssuedCert into a live rustls::ServerConfig for the account HTTP face is the job of B3 (the credential-free origin, #1165); A3 stops at the issuance contract and its monitoring.

Structs§

CertHandle
A live, hot-swappable handle to the currently-served account-zone cert.
IssuedCert
A DER-encoded wildcard certificate + its private key, freshly issued.
NullWildcardCertIssuer
Fail-closed issuer for deployments that wired no ACME-DNS-01 backend.

Enums§

IssuanceError
An error from the DNS-01 wildcard issuance path.

Traits§

WildcardCertIssuer
The interface a deployment’s DNS-01 wildcard issuer implements.

Functions§

require_provisioned
Validate that the deployment has provisioned DNS-01 wildcard issuance.