Project ideas from Hacker News discussions.

Let's Encrypt is adding two additional remote perspectives for domain validation

📝 Discussion Summary (Click to expand)

1. BGP hijacks expose limits of multi‑perspective validation and RPKI adoption
The discussion repeatedly notes that even Let’s Encrypt’s multi‑perspective checks failed when a bogus route was RPKI‑invalid yet still accepted by most of the Internet.

“For 33 hours in late August, a rival network hijacked a block of Hetzner‑hosted infrastructure … The stolen route was RPKI‑invalid the entire time, on file, checkable by anyone. It still won on most of the internet.” – throw0101a
“70% adoption doesn't seem high enough … to be a mandatory component of validation.” – woodruffw

2. Current domain‑validation methods are unreliable or merely “security theater”
Critics argue that HTTP‑01 and even DNS‑01 challenges can be subverted, and that the existing process adds little real security beyond a band‑aid.

“http‑01 seems absolutely unreliable, any hosting provider or any government can issue fake certificates using it. What a garbage technology.” – codedokode
“I went through the standard validation many times and the entire process felt like a security theater.” – mopsi
“checking from multiple perspectives is a good idea, but still ultimately a band‑aide over the top of a flawed system. A properly engineered solution would need to ultimately come down to cryptographic proof of domain ownership.” – Ajedi32

3. Let’s Encrypt’s role in democratizing HTTPS and pushing short‑lived certificates
Many commenters credit Let’s Encrypt (and the Snowden‑era push for ubiquitous encryption) with making HTTPS cheap and automatic, while noting its shift toward very short validity periods.

“It is wild to think that enabling HTTPS used to be difficult and expensive before Let's Encrypt came along in the wake of the Snowden revelations.” – Schlagbohrer
“The most radical thing LE did was not to provide free certs, or even automated certs, but short‑lived certs.” – autoboy
“That summer, Edward Snowden came forward with chilling revelations about NSA mass surveillance, and the need for ubiquitous encryption became clearer than ever.” – onionisafruit (quoting J Alex Halderman)


🚀 Project Ideas

Generating project ideas…

RPKI‑Guard for ACME Validation

Summary

  • Detects BGP hijacks by verifying RPKI validity of the IP address returned during ACME domain‑control validation before allowing certificate issuance.
  • Provides an automated safety net that blocks fraudulent certs even when multi‑perspective validation is fooled by a spoofed destination.

Details

Key Value
Target Audience Certificate Authorities, DevOps teams, security‑conscious website operators
Core Feature Real‑time RPKI ROV check on the resolved A/AAAA record during HTTP‑01/TLS‑ALPN‑01 challenges; optional alerting or automatic abort
Tech Stack Go (core agent), Prometheus‑compatible metrics, RPKI‑RTR client library, plugins for Certbot/lego, Docker
Difficulty Medium
Monetization Revenue-ready: SaaS subscription tiered by validation volume (free tier up to 1k validations/mo)

Notes

  • HN users highlighted the gap: “If the network as a whole thinks the destination is someplace else then all those paths will lead to the same (false) location.” (throw0101a)
  • Offers a concrete way to add “MUST” RPKI validation to the CA pipeline, addressing the call for stronger domain‑ownership proofs without relying solely on multiple vantage points.

DNSSEC‑ACME Bridge

Summary

  • Automates the DNS‑01 ACME challenge using DNSSEC‑signed records, providing cryptographic proof of domain ownership that resists BGP‑based hijacks.
  • Works as a drop‑in wrapper around existing ACME clients (Certbot, lego) to require DNSSEC validation for every renewal.

Details

Key Value
Target Audience Sysadmins, hosting providers, security teams seeking stronger domain validation
Core Feature Generates and publishes DNSSEC‑signed TXT records for the ACME token, validates signatures on the resolver side before proceeding
Tech Stack Python (dnspython, ldns bindings), integration with OpenDNSSEC or PowerDNS for signing, CLI plugin architecture
Difficulty Medium
Monetization Hobby (open‑source) – optional paid support/managed DNSSEC signing service

Notes

  • Commenters asked for “cryptographic proof of domain ownership (whether through DNSSEC, or something similar)” (Ajedi32) and lamented that “http‑01 seems absolutely unreliable.” (codedokode)
  • Directly satisfies the desire for a validation method that cannot be subverted by spoofing the destination IP, giving HN readers a practical tool to discuss and deploy.

EasySMIME – Personal S/MIME Certificate Manager

Summary

  • Provides free, automated S/MIME certificates for individual users, with private keys generated and stored locally (or on a hardware token) and renewed transparently.
  • Integrates with major email clients via native plugins or a lightweight daemon that handles provisioning, key backup, and restore.

Details

Key Value
Target Audience Privacy‑conscious individuals, journalists, small‑business owners wanting encrypted email
Core Feature ACME‑style endpoint that issues S/MIME certs (using RFC 8823 extensions) after email‑address ownership proof; client‑side key generation, optional YubiKey/OpenPGP smartcard support
Tech Stack Rust daemon (tokio), WebAssembly UI for browser‑based management, libsodium for key backup, plugins for Outlook/Apple Mail/Thunderbolt via native messaging
Difficulty High
Monetization Revenue-ready: Freemium – free basic issuance, paid tier for premium support, hardware‑token bundling, and enterprise‑scale key‑management APIs

Notes

  • HN discussion expressed strong need: “We really need a CA that does for mail what Let's encrypt has done for HTTP” (Tepix) and highlighted key‑management pain points for personal PGP/ S/MIME (betterunix2).
  • By delivering a Let’s Encrypt‑like experience for S/MIME with user‑controlled keys, the project directly addresses the frustrations around key handling and limited adoption, sparking practical utility and debate among security‑focused readers.

Read Later