Cascadity Audio
← All streams

#tls

Everything tagged tls, across every stream.

0

Apple's command-line git, curl and python3 still trust the compromised eMudhra certificates, researchers warn

The page includes a one-line check (and a safe demo) to see if your Mac's git can be fooled; Apple's support note explains the manual fix.

Follow-up to last week's eMudhra breach, in which the private keys of eight of the Indian certificate authority's intermediate CAs were compromised. A community site run by Dennis Jackson says that as of October 28, the developer tools Apple ships with macOS, including git, curl and python3, still accept certificates from those CAs, 11 days after Apple was notified. It says macOS 27.2, released October 26, did not fix this and undid the manual workaround. Because anyone holding the keys can mint a certificate for any site, it argues that an attacker on the network path could intercept git clones and pushes or capture tokens; the page offers a test repository that impersonates GitHub.

Apple's support note says it has blocked the 12 affected certificates in Safari, Mail and apps using its networking frameworks since October 19, and the emSign ECC Root CA - G3 since October 23. It confirms that tools such as curl and git check /etc/ssl/cert.pem and can still accept these certificates until a future software update, and gives steps to remove the roots by hand.

On Hacker News, some argued the title should blame the shared certificate file rather than git, and one commenter said the threat is overblown because an attacker needs a network position first.

Rabbit Holes 2
0

r/cybersecurity: eight eMudhra TLS certificates found with private keys only a few bits long

Why a single weak certificate authority can matter to everyone, and the long cleanup ahead.

The post links Ars Technica's report that eight intermediate TLS certificates belonging to the India-based certificate authority eMudhra had private keys of only 3 to 8 bits (a normal P-384 key has about 384 bits), so anyone could use them to issue certificates that browsers and apps would trust for any site. Ars says browser makers and some major apps and programming languages had blocked all eight by Tuesday, with no sign yet of malicious use in certificate transparency logs, but cryptography engineer Filippo Valsorda called it "a massive cleanup job, bigger than Heartbleed," because of Linux distributions, containers and IoT devices. Exploiting it requires intercepting traffic.

Replies from defenders range from gallows humor about ruined evenings to disbelief at the key sizes. Others question why systems automatically trust so many certificate authorities, and note that the certificates had been cross-signed by Sectigo. About 3,100 upvotes in a 1.1-million-member community.

Rabbit Holes 2
0

eMudhra's certificate authority keys turn out to be single-byte numbers, and it quits the global TLS business

One of the keys trusted by every major browser was the number 4. Scott Helme explains why that cannot be fully contained.

A researcher proved that the private keys of eight eMudhra intermediate certificate authorities, chaining to roots trusted by Mozilla, Microsoft, Apple and Chrome, were compromised, and reported it on October 17. The disclosure site says the keys were incorrectly generated and anyone could recover them from the certificates since April 2025. Security researcher Scott Helme says each key was a single byte (one was literally 4) and he recovered all eight in under a second. Browsers blocked the intermediates within days, and because no certificates from them appeared in Certificate Transparency logs, CT-enforcing browsers were protected, but curl, Python, Go, CI pipelines and embedded devices that don't check revocation or CT need updated CA bundles.

On October 22 eMudhra said it will exit the global SSL/TLS business, about 1% of its revenue, saying it revoked the CAs within 14 hours, no end-entity certificates were issued from them, and scrutiny was out of proportion.

Three Hacker News threads questioned how a CA passed audits with such keys, debated whether the web's CA system needs replacing, and criticized eMudhra's statement.

Rabbit Holes 2
  • Certificate Transparency

    After exploring Eight Bits of Trust; eMudhra's CA keys cracked in milliseconds, to see why browsers were shielded and other software was not, read about Certificate Transparency.

    An internet security standard for monitoring and auditing the issuance of digital certificates, so mis-issued certificates can be spotted.

    Wikipedia · Wade · 5 min

    0
  • How It Works

    After exploring eMudhra Intermediate CA Compromise, for how certificates are normally issued, read How It Works.

    Let's Encrypt walks through how a web server proves to a certificate authority that it controls a domain and then requests or revokes certificates, using the ACME protocol.

    Let's Encrypt · Swim · 30 min

    0