Skip to content

upki fetch produces (unsupported) clubcard v3 filters #10

Closed

Description

@philhofer

I've got upki fetch wired up as a systemd timer to populate /var/cache/upki exactly as it is packaged in nixpkgs unstable.
I had assumed that I could point upki.NewChecker to /var/cache/upki to have a working configuration, but evidently not:

    upki_test.go:22: Head "https://google.com": upki: parsing filter 20261017-1-default.filter: crlite: unsupported clubcard version: 3

I understand that this code only supports v4 clubcards, but I'm unclear what needs to change here to get things working. Should upki fetch be reconfigured to fetch only v4 clubcards? (Is that even possible?) Should this package ignore v3 clubcard files? Something else?

EDIT: in case it's helpful:

; jq '.generated_at, .comment' < /var/cache/upki/revocation/manifest.json
1793104124
"rustls/upki run 40504012486"

Activity

  1. cpu commented on Oct 27, 2026

    @cpu
    Owner

    Hi, thanks for opening this issue.

    I think there's a few things going on, but I believe setting services.upki.settings.revocation.fetch-url = "https://upki.rustls.dev/revocation/"; in your config and making sure you fetch new cache data should resolve the issue. I'll open an upstream NixPkgs PR to make that change more broadly.

    To summarize the state of things:

    1. The upstream Firefox CRLite channel that upki mirror fetches as its authoritative source of data is still using v3 clubcard data, and won't transition to v4 for some time.
    2. With that in mind, I updated the tooling to re-encode the v3 data to v4 automatically: mirror: improved channel handling, v3 -> v4 reencoding support rustls/upki#268
    3. We've merged that update, so the https://upki.rustls.dev/ mirror has v4 data, but the mirror has two sets of data, the legacy bits at the root that are pre-1.0 and are in V3 encoding because the V4 decoder hadn't landed yet and there were extant clients pointed there, and then under /revocation is the V4 data, and we made that the default URL in 1.0+.
    4. The NixOS module (at least in unstable) is using upki 1.0+ and supports V4, but the module configuration is still incorrectly pointed at the legacy root not the /revocation subdir
  2. cpu commented on Oct 27, 2026

    @cpu
    Owner

    I believe setting services.upki.settings.revocation.fetch-url = "https://upki.rustls.dev/revocation/"; in your config and making sure you fetch new cache data should resolve the issue.

    One other note: since both sources have the same modified date atm you'll need to remove the old cached data (or just the manifest.json) first, or wait for the next update. Otherwise it won't replace the v3 content with v4 content since it hasn't changed since the last fetch.

  3. philhofer commented on Oct 27, 2026

    @philhofer
    Author

    Great, thanks! I've adjusted the configuration, cleared the cache directory, restarted the timer, and no longer receive that error.

    I do, however, notice that google.com is using an uncovered cert:

    upki_test.go:22: Head "https://www.google.com/": cert chain 0 has an uncovered cert
    

    I suspect the cert may be too new but I'll have to dig further. I was hoping to have my TLS configuration reject uncovered certs by default.

    Anyway, I'll mark this as closed.

  4. cpu commented on Oct 27, 2026

    @cpu
    Owner

    Great, thanks! I've adjusted the configuration, cleared the cache directory, restarted the timer, and no longer receive that error.

    Thanks for confirming! Here's the upstream change: NixOS/nixpkgs#579713

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions