3 ms·
> 1. WHOIS isn't encrypted or signed, but is somehow suitable for verification (?) HTTP-based ACME verification also uses unencrypted port-80 HTTP. Similar for
by account42 2y ago
> 1. WHOIS isn't encrypted or signed, but is somehow suitable for verification (?)
HTTP-based ACME verification also uses unencrypted port-80 HTTP. Similar for DNS-based verification.
- iscoelho 2y ago100% - another for the BGP hijack!
- michaelt 2y agoThe current CAB Forum Baseline Requirements call for "Multi-Perspective Issuance Corroboration" [1] i.e. make sure the DNS or HTTP challenge looks the same from several different data centres in different countries. By the end of 2026, CAs will validate from 5 different data centres. This should make getting a cert via BGP hijack very difficult. [1] https://github.com/cabforum/servercert/blob/main/docs/BR.md#3229-multi-perspective-issuance-corroboration https://github.com/cabforum/servercert/blob/main/docs/BR.md#...
- tialaramex 2y agoIt is hypothesised to make this more difficult but it's unclear how effective it is in practice. I wouldn't expect it to make a significant difference. We've been here before.
- iscoelho 2y agoSee my post above about BGP hijacks: https://news.ycombinator.com/item?id=41511582 https://news.ycombinator.com/item?id=41511582 - They're way easier than you think.
- bootsmann 2y ago> HTTP-based ACME verification also uses unencrypted port-80 HTTP I mean, they need to bootstrap the verification somehow no? You cannot upgrade the first time you request a challenge.
- Arch-TK 2y agoIf it used HTTPS you would have a bootstrapping problem.