An important article to read in the aftermath of the eMudhra certificate disaster is [Wayback/Archive] The Real Risks of eMudhra | IFIN.
Starting from the browsers – most of these should not be affected any more – it continues with the non-browsers, especially the kind of equipment that will never be updated, explaining how they can be part of an attack (and a blessing – hello pesky TV manufacturers showing ads on the equipment we bought), the terminals you type commands in, software development stacks implementing their own certificate stores and many many other entry points. Then mitigations are covered, basically the good old CMDB is new and shiny again, and the most important bit: have a plan for next time. As there will be a next time.
The blog post goes hand in hand with observations like for instance [Wayback/Archive] Jan Schaumann: “I just ran a check across / on my mac and found 43 #emudhra vulnerable vendored bundles. …” – Mastodon 🐘





