Skip to content

Qertum 1.0.0

Latest

Choose a tag to compare

@tomgron tomgron released this 11 Nov 17:03
Immutable release. Only release title and notes can be modified.

Qertum 1.0.0

The first stable release. From this version the
support and compatibility policy applies: it says what a
version number promises and which releases get security fixes. Qertum stays free software under the MIT licence,
provided as is; no support plan is sold.

Security

  • Automatic renewals revoke what they replace. ACME and EST renewals that are approved automatically now honour
    AutoRevokeOnRenewal, as manual approval already did: the replaced certificate is revoked with reason
    superseded.
  • Concurrent revocations keep the winning reason. Two revocation requests for the same certificate can no
    longer overwrite each other's reason or side effects.
  • CA keys at rest are always encrypted. Startup encrypts legacy plaintext CA key files, including per-issuer
    files, with the Data Protection key ring, replacing them atomically with owner-only permissions.
  • TPM wrapping keys never touch disk. Sealing and unsealing pass the wrapping key through process pipes instead
    of temporary files.
  • Multi container: CA hosts no longer see identity or web state. API, ACME, EST and the queue consumer see
    /data/identity and /data/web as empty; API and the queue consumer read only the identity audit logs.
  • Shorter access tokens. The built-in identity provider issues access tokens valid for 10 minutes instead of an
    hour (IdentityService__AccessTokenLifetimeMinutes, 1 to 60), so a disabled, deleted or demoted user loses API
    access within that time.
  • Permission changes reach every API instance. When the shared cache cannot be read, role permissions are read
    from the database instead of a cached copy.
  • The first settings save cannot weaken PQC enforcement. The PQC stage starts at Enforce and only an
    administrator changes it.
  • ACME http-01 never uses a proxy, so the challenge address policy checks the address actually connected to.
  • ACME renewals need an issued predecessor to qualify for the Pilot-stage classical-key exception.
  • Bulk operations without a stable creator are administrator-only.
  • Sign-in input is bounded: usernames up to 256 and passwords up to 1024 characters.
  • The web UI's localhost development addresses are registered with the built-in identity provider only in
    Development.
  • qca replaces terminal control characters in server text with ? and writes key files without following a
    symbolic link at the output path.
  • Logs name issuers by ID in the CRL supersession message, not by their user-controlled name.
  • Patched .NET runtime. Both images now build on ASP.NET Core 10.0.15, which fixes the November 2026
    ASP.NET Core advisories, among them an elevation of privilege in the connection layer that Blazor's web UI uses
    (CVE-2026-114146) and a denial of service (CVE-2026-114147). ASP.NET Core, EF Core and the cryptography packages
    move to 10.0.15 too.
  • Source builds: Aspire 13.6.5. The AppHost and its packages move to Aspire 13.6.5, which fixes a dashboard
    cookie leak to a linked container (CVE-2026-120006). The Aspire CLI must be 13.6.5 or newer too
    (CVE-2026-120778, CVE-2026-120792). This concerns local development only: the release images do not contain
    Aspire.

Changed

  • The cache is named Valkey throughout. The multi-container image reads the cache address from VALKEY_ADDRESS;
    the old REDIS_ADDRESS still works.
  • Step-up during onboarding. When step-up authentication is on, the onboarding pages ask for a fresh sign-in
    instead of failing.
  • Issue forms on GitHub. Bug reports and feature requests use forms, and questions go to the
    Q&A category of GitHub Discussions. Report a
    vulnerability by email as SECURITY.md describes, never in a
    public issue.

Verified for this release

  • Full test suite, local CodeQL (security and code quality) and the security scan of both layouts, with the browser
    check in Chromium, Firefox and WebKit.
  • Upgrade from 1.0.0-rc7 on the same data volume.
  • The post-quantum compatibility matrix on x86_64 as well as arm64: all 33 Linux cells give the same verdict on both
    architectures, and the .NET cell now has a Linux x64 run.
  • TPM secret storage on real hardware in both layouts, as a non-root user: one x86_64 firmware TPM 2.0 (Microsoft
    Pluton). Clearing or replacing a TPM was tested on software TPMs only. Discrete TPM chips, other firmware TPMs and
    arm64 are untested.
  • Step-up with Keycloak 26.8.1: the web UI's reauthentication works. The tested Keycloak device flow does not
    produce the required MFA level, so qca step-up against Keycloak is refused; see
    Identity Providers.

Upgrading

  • Back up /data first. This release adds no database migration over 1.0.0-rc7.
  • Multi container: refresh your copy of deploy/multi-container/ from this release before
    docker compose up -d. The data initializer is now the container qertum-data-init, and the backup and restore
    wrappers take the volume from it. With the bind override, refresh docker-compose.bind.yml too.
  • Access tokens of the built-in identity provider now last 10 minutes; the web UI and qca renew them on their own.
  • Every change is listed in Upgrading.