2 ms·
For Domain Fronting in particular it's embarrassing that pro-distributed people have taken it as a "victory" that AWS and Google disabled domain fronting used a
by tialaramex 7y ago
For Domain Fronting in particular it's embarrassing that pro-distributed people have taken it as a "victory" that AWS and Google disabled domain fronting used as an anti-censorship mechanism for Signal. That's both a terrible look "Ha! Our services are so unpopular nobody even cares to block them" and a grave misunderstanding of the situation.
The big CDNs and cloud service providers are actually very enthusiastic about domain fronting, what they blocked was the technical mechanism abused to make it happen, because it causes their reliability teams pain. Domain fronting means you figure out this is a request for thing-a.example.com using SNI, your backend systems cue up the Thing A service... and then during HTTP headers the client insists it intended to talk to thing-b.example.com all along instead and you've got to either give an error or somehow backtrack and make that happen. Doing this is very easy, indeed the default, in say one Apache httpd on a Linux box. But Google or AWS isn't a data centre full of Apache httpds on Linux boxes, it's a bit more complicated than that.
When I say they're enthusiastic I don't mean just empty words, the active direction of QUIC, eSNI, the revised HTTP service record for DNS and so on are all aligned with the domain fronting concept, just not in the form of abusing different protocol layers. They want to know early in the connection which service you're intending to reach, while preserving your privacy from snooping governments, etc.