Hacker News Reader

Comment by mpartel | Hacker News Reader

I realized I glossed over the fact that this would put other AWS/GAE customers's money at risk too. This complicates matters somewhat, and some (I believe a negligible number of) customers might switch to an unblocked competitor.

Personally this weakens my view a little, but is not enough to change it substantially.

View on HN

The ethical choice is for AWS and Google to collude and both allow signal to continue to using domain fronting.

Great PR opportunity for Cloudflare to pickup the torch.

EDIT: Not supported by Cloudflare.

Cloudflare is against domain fronting https://arstechnica.com/information-technology/2018/04/googl...

Despite the use case for censorship circumvention, many malware command and control bots use domain fronting to bypass corporate web filters that otherwise might block their traffic. CloudFlare, being a security-focused CDN, most definitely does not want to help enable malware authors to bypass security.

Russia had no problem whatsoever blocking both of them when blocking Tether a couple weeks ago.

No problem? They crippled their own use of the internet, at huge financial cost.

Where do you get that from? The Russian government blocked lots of AWS and Google IPs, and had no problem keeping them blocked until they agreed to stop allowing this, which was the same thing Telegram was using. And it doesn't appear that they cared about the "huge financial cost".

Reply on news.ycombinator.com