3 ms·
This relates into the problem first highlighted for Let's Encrypt's tls-sni-01 (and tls-sni-02 but that never entered production use) validation methods, which
by tialaramex 9y ago
This relates into the problem first highlighted for Let's Encrypt's tls-sni-01 (and tls-sni-02 but that never entered production use) validation methods, which cascaded into the entire method 10 of the Ten Blessed Methods.
To recap that: Several popular CDNs or bulk virtual hosts let you type in any hostname and say you're going to host it with them. They figured that if the people who really own that name don't agree, they just wouldn't point their DNS records to the relevant servers and so it's fine. Let's Encrypt's tls-sni family of validations do a DNS lookup for the name to be validated, but then request SNI for a different invalid hostname as a signal. If a CDN or bulk host used for say, example.com allowed another customer on their service to say they wanted the invalid hostname as their "real" name, they could pass the tls-sni validation for example.com and get a certificate issued.
Naively we often assume that it's OK to let users pick names in a service without taking any step to validate that the person asking is entitled to the name. We may even kid ourselves that the custom name doesn't implicitly convey any legitimacy, that @MileyCyrus might be just some 14 year old from Swansea named Miley Cyrus, that mcdonalds.com could be a family web site of the McDonald clan, or that security@gmail.com could just be some bloke who works the doors at a local nightclub. But the reality is that users think names convey meaning even if you specifically tell them otherwise.
GitLab won't be the first to get bitten by this, and they won't be the last.
- ben_jones 9y agoIsn't this the case with most hosting providers, such as Digital Ocean? You point your registrar's name servers at ns1, ns2,ns3.digitalocean.com then create requisite DNS records for a given droplet. Seems like the same lack of authentication.
- Ajedi32 9y agoThe difference is that DigitalOcean gives each VM its own IP address. So even though your DNS may be pointed at DigitalOcean's servers, other DigitalOcean customers are not able to respond to incoming TLS connections for that IP.