Menu

1 / 3

Check if eMudhra CA Is Still Trusted in Your Runtime

#sitepoint#emudhra#system#store#chain
Reading 0:00
15s threshold

The AI briefing for Developers

Stay up to date with AI tools, model releases, and developer workflows that matter.

Weekly. Free. One click to leave.

How to Check If Compromised eMudhra CAs Are Still Trusted

Identify every runtime in your stack that makes outbound TLS connections (curl, Python, Node.js, Go, Rust, containers).

Run each runtime's TLS client against the official per-intermediate test endpoints (for example https://dv-g3b-emudhra.we-have-a-problem.com/ ) to test for trust of the compromised intermediates.

Obtain the incident's test certificate chains - the research disclosure site linked in Scott Helme's post is the canonical starting point - and verify their integrity before trusting them offline.

Verify each extracted PEM chain offline against your system and bundled CA stores using openssl verify .

Update system CA packages ( ca-certificates ), language-level bundles ( certifi , webpki-roots ), and runtime versions.

Rebuild Docker images and CI environments with updated base images…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.