Skip to content

fix: apply Azul eMudhra blocklist to the jlinked JRE - #57

Closed
aaron-steinfeld wants to merge 1 commit into
mainfrom
alt/blocked-certs-overlay
Closed

aaron-steinfeld wants to merge 1 commit into
mainfrom
alt/blocked-certs-overlay

Conversation

@aaron-steinfeld

Copy link
Copy Markdown
Contributor

Smaller alternative to #55 (and a stopgap next to #56): keep the current Zulu images and overlay Azul's published blocklist, per https://docs.azul.com/core/emudhra-workaround.html.

  • Vendors Azul's emudhra-block-unix.certs as java-11/blocked.certs and java-21/blocked.certs.
  • After jlink, each Dockerfile verifies its SHA-256 (2596bb6d…bf10) and copies it over /jre/lib/security/blocked.certs with mode 644. It has to run after jlink, which takes blocked.certs from jmods, so an overlay on the JDK before jlink would be lost.
  • The file has the same 86 fingerprints as blocked.certs in Zulu 11.0.33 and 21.0.13, and is a superset of the lists in 11.0.32.1 and 21.0.12.1, so nothing is dropped.
  • No base image, java.version or workflow changes, and no CA roots are deleted (unlike Delete unwanted CA certificates in Dockerfile #55). No network fetch at build time.

Limits:

Tested by building java-11 and java-21 for linux/arm64. The hash check passes, and the installed file in each image matches Azul's hash with mode 644. amd64, the Trivy scan, and a forged-chain rejection test were not run.

🤖 Generated with Claude Code

Overlay Azul's emudhra-block-unix.certs (SHA-256 verified) onto
/jre/lib/security/blocked.certs after jlink, since jlink takes the list
from jmods. Same 86 fingerprints as Zulu 11.0.33 / 21.0.13. Temporary
until the base image is on a fixed Zulu release.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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