← All stories
● Covered by 1 source · 1 reportLow impact1 negative

Critique of SSL/TLS Certificate System and a 'Protest Certificate' Implementation

🔄 Updated 11d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • SSL/TLS certificates require complex ACME processes and frequent renewals.
  • Certificates are issued over plaintext, and some CAs have used weak keys.
  • Author created a 'protest certificate' with a custom, non-random public key.
  • The public key contains an embedded message, showing lack of validation.

Critique of SSL/TLS Complexity

The author criticizes the current SSL/TLS system, highlighting the complexity of the ACME protocol required for certificate issuance. A significant point of contention is the frequent expiration of certificates, necessitating constant maintenance even with automation, as ACME clients require continuous access to DNS records or web servers.

Security Flaws in Certificate Issuance

Further concerns are raised regarding the security of the certificate issuance process itself. The author notes that certificates are issued over plaintext connections and points out past instances where trusted certificate authorities have used insecure keys, such as the number '4', for extended periods.

The 'Protest Certificate' Concept

While acknowledging the need for encrypted web traffic to prevent passive eavesdropping, the author argues that the entire certificate validation system is unnecessary for this goal. As a form of protest, a 'protest certificate' was created. The only part of the certificate directly controlled by the user is the public key.

Demonstrating Lack of Public Key Validation

Instead of using a cryptographically random private key, the author generated a public key that visibly embeds a message: 'You don't actually have to pick random private keys. No one checks these things. A certificate authority got away with the number 4 for a year.' This demonstrates that certificate authorities do not verify the randomness or content of the public keys they sign, allowing for non-standard or even intentionally weak keys to be certified without detection.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

The author expresses frustration with the complexity and perceived flaws of the SSL/TLS certificate system, citing frequent expirations and issuance over plaintext. As a form of protest, the author created a certificate with a public key containing an embedded message, demonstrating that certificate authorities do not validate the randomness or content of public keys.