Skip to content

chore: Remove certificate package cooldown exemptions - #205

Closed
fstagni wants to merge 2 commits into
DIRACGrid:mainfrom
fstagni:chore/remove-certificate-cooldown-exemptions
Closed

fstagni wants to merge 2 commits into
DIRACGrid:mainfrom
fstagni:chore/remove-certificate-cooldown-exemptions

Conversation

@fstagni

@fstagni fstagni commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #204: once the security releases for the eMudhra/emSign CA key compromise (CVE-2026-111943) are older than 7 days, the temporary exclude-newer exemptions for certifi, ca-certificates and pip are no longer needed and the default release cooldown protection is restored.

 pixi.toml [exclude-newer]
   constructor = "0d"
-  ca-certificates = "0d"
-  certifi = "0d"
-  pip = "0d"

The patched versions (certifi 2026.10.23, ca-certificates 2026.10.23, pip 26.2.2) remain in pixi.lock: removing the exemptions does not re-resolve existing entries, it only applies to future updates.

Merge after #204 — this branch is stacked on top of it.

Evidence

$ git diff main..HEAD -- pixi.toml   (after #204 merges)
only the 3 exemption lines removed; constructor exemption untouched

pixi.lock is unchanged by this PR (verified: no diff).

Merge Danger

Door: two-way (restores the previous, more conservative behaviour; trivially revertable)

Blast Radius: future dependency updates only. Re-enabling the cooldown means newly released packages wait 7 days before being picked up, which is the intended protection against freshly-published (potentially compromised or broken) versions. Deliberate security updates will need a temporary exemption again, as in #204.

The private keys of eight eMudhra/emSign intermediate CA certificates
were disclosed as compromised on 2026-10-20 (CVE-2026-111943).

- Require certifi >=2026.10.19 and ca-certificates >=2026.10.19, which
  remove the compromised emSign roots (the unaffected emSign Root CA - G1
  is retained).
- Require pip >=26.2.2: pip vendors its own certifi bundle and trusts it
  in addition to the system store, so older pip stays vulnerable.
- Exempt these packages (plus pip) from the 7-day release cooldown in
  pixi.toml, otherwise the security releases would be blocked.
The temporary exemptions for certifi, ca-certificates and pip were only
needed to let the eMudhra CA compromise security releases (CVE-2026-111943)
through the 7-day release cooldown. They are no longer needed once those
releases are older than the cooldown window, so the default protection is
restored.

The patched versions remain in pixi.lock: removing the exemptions does not
re-resolve existing entries, it only applies to future updates.
@fstagni

fstagni commented Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

Closing for now: this should only be opened after #204 is merged. The branch chore/remove-certificate-cooldown-exemptions is kept on the fork so the PR can be recreated immediately afterwards.

@fstagni fstagni closed this Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant