Cascadity Audio
← All streams

#cryptography

Everything tagged cryptography, across every stream.

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
0

Claude traces the mysterious NIST elliptic-curve seeds to a 1990s random number generator seeded with timestamps

A 25-year cryptography mystery, solved by reverse-engineering a weak PRNG; the write-up walks through how.

Anthropic says an internal research model worked out, in under half an hour, how the unexplained 'seed' values behind the NIST P-192, P-224, P-256, P-384 and P-521 curves were made. The NSA supplied them around 2000 without explanation, which fed long-running suspicion of a backdoor; lore said they were hashes of a joke phrase. Instead, Anthropic says, they are output of the C library's lrand48 generator seeded with Unix timestamps from May 1997 to April 1998, and it also explained the base points of some curves. Anthropic stresses this is not an attack and makes deliberate weakening much less plausible. Cryptographer Filippo Valsorda, who offered a bounty for the answer, says it has been claimed, with the prize donated to the nonprofit behind Let's Encrypt.

On Hacker News, some noted the method still doesn't rule out cherry-picking among many timestamps; others worried that labs can use capabilities the public is blocked from; many simply enjoyed the end of a long-running conspiracy theory.

Cascadic Analysis 1
UndertowAutonomous cyber capability scales attackers enormously

What hidden risk could pull against this, even if the news is good?

The answer, Anthropic says, was a C library generator seeded with Unix timestamps, a classic way randomness goes wrong, and its model found it in under half an hour after decades of human guessing. Here it cleared up a suspicion rather than breaking anything. The same skill pointed at keys or tokens that some other system generated from a guessable seed would be an attack, and Hacker News commenters noted that labs can use capabilities the public is blocked from.

0
Rabbit Holes 2
  • Dual EC DRBG

    After exploring Claude reveals ECDSA curve origins, for the history that made people suspicious, read about Dual EC DRBG.

    A NIST-standardized random number generator criticized for a possible NSA backdoor, withdrawn in 2014; part of why the curve seeds drew suspicion.

    Wikipedia · Swim · 30 min

    0
  • Elliptic-curve cryptography

    After exploring Claude reveals ECDSA curve origins, for the basics of the math being protected, see Elliptic-curve cryptography.

    Public-key cryptography based on elliptic curves over finite fields, which allows smaller keys than RSA for equivalent security.

    Wikipedia · Wade · 5 min

    0