Skip to content

Added oficial eMudra verifier by oracle, however I had never seen it pass - #53

Merged
judovana merged 3 commits into
mainfrom
szdfgzdf
Oct 27, 2026
Merged

judovana merged 3 commits into
mainfrom
szdfgzdf

Conversation

@judovana

@judovana judovana commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

On fixes portbales, or on rpms with updated system cacerts.

FAILED: reproducers/emudra/CheckCerts.java
Passed: reproducers/emudra/Main.java

Output is:

Java runtime version 25.0.4.1+1 at /usr/lib/jvm/java-25-openjdk
BAD ROOT: CN=emSign Root CA - G1,O=eMudhra Technologies Limited,OU=emSign PKI,C=IN

On unpatched portables/rpms with nonupdated system cacerts

FAILED: reproducers/emudra/CheckCerts.java
FAILED: reproducers/emudra/Main.java

Output is

Java runtime version 25.0.5+8-LTS at /home/jvanek/git/jtreg-buffer/java-25-openjdk-25.0.5.0.8-2.0.portable.jdk.x86_64
BAD ROOT: CN=emSign ECC Root CA - G3,O=eMudhra Technologies Limited,OU=emSign PKI,C=IN
BAD ROOT: CN=emSign Root CA - G1,O=eMudhra Technologies Limited,OU=emSign PKI,C=IN

So there is change.. however...

@judovana

judovana commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator Author

@zzambers / @franferrax thoughts?

@zzambers

Copy link
Copy Markdown
Contributor

Seems to me that updated cacerts block compromised intermediate certs, while this test expects root certs, which issued those, to be also blocked.

i.e. here updated cacerts only block Intermediate CA column, while test expects ones in chains to column to be blocked:
https://emudhra.we-have-a-problem.com/#check

I could be wrong.

@zzambers

zzambers commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

According to wikipedia article, major browsers first blocked compromised certs, later also blocked roots:

... Google Chrome and Firefox blocked the certificates within hours of the report. Apple followed on October 19 and Microsoft on October 20. eMudhra revoked the eight certificates. Google said none of the six TLS intermediates had issued certificates recorded in Certificate Transparency logs, and eMudhra said only one of the eight had been put into use and none had issued certificates to customers. On October 20, Mozilla removed the root certificate that had issued them, emSign ECC Root CA – G3, from NSS, and on October 21, Google stated that Chrome would also remove the root certificate from its Chrome Root Store by the morning of October 27. ...

@zzambers

zzambers commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Reading description again,

this one actually seems to get blocked with patched cacerts:
CN=emSign ECC Root CA - G3,O=eMudhra Technologies Limited,OU=emSign PKI,C=IN

and only this one fails:
CN=emSign Root CA - G1,O=eMudhra Technologies Limited,OU=emSign PKI,C=IN

code says

        // Other eMudhra roots, not related to the compromised intermediates
        "emSign Root CA - G1",
        "emSign Root CA - G2"

so oracle probably expects all eMudhra root certs blocked. (even those not related to compromised certs)

@judovana

judovana commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator Author

According to wikipedia article, major browsers first blocked compromised certs, later also blocked roots:

Oh. Correct!

In that case I will not merge untill the release iout, to not compromise results.

Comment thread test/reproducers/emudra/CheckCerts.java Outdated
Comment on lines +52 to +54
// Other eMudhra roots, not related to the compromised intermediates
"emSign Root CA - G1",
"emSign Root CA - G2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @judovana. We incidentally discussed this test on a meeting earlier today. It seems OpenJDK went beyond and removed these non-compromised CAs, but RHEL's ca-certificates kept them.

So OpenJDK RPMs on RHEL will still find these two from the system CA, making the test fail. I suggest applying @fitzsim's changes from the version attached to this internal email:

Suggested change
// Other eMudhra roots, not related to the compromised intermediates
"emSign Root CA - G1",
"emSign Root CA - G2"
// Other eMudhra roots, not related to the compromised intermediates
// RHEL cacerts retains these (for now), so skip them.
// "emSign Root CA - G1",
// "emSign Root CA - G2"

Keeping original strict version in disabled state
@judovana
judovana merged commit b053a57 into main Oct 27, 2026
0 of 38 checks passed
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.

3 participants