Oh boy. I wonder how many other companies that have previously been lax about validating that cert revocation is handled correctly by their devices are going to validate the eMudrha cert revocation and discover that they are not, in fact, handling revocation correctly. Yikes.
This caught my eye, remember how the eMudhra certificates had weirdly low parameters, like 4 and others in the single digits?<p>"Mbed TLS - Medium, CVSS 5.9 - A buffer-length typo reduces a 2048-bit DH modulus to one byte. TLS 1.2 DHE_RSA sessions are decryptable when the client accepts the broken parameters. GOAHEAD-SA-2026-0005."<p>Not familiar with those implementation details but was this the root cause?
Internet infrastructure companies using '5' as their private key are sweating bullets. They know they are next.
[flagged]
[flagged]
nice i abs like this