Slashdot Mirror
Google Is Shuttering Domain Fronting, Creating a Big Problem For Anti-Censorship Tools (theverge.com)
"The Google App Engine is discontinuing a practice called domain fronting, which lets services use Google's network to get around state-level internet blocks," reports The Verge. While the move makes sense from a cybersecurity perspective as domain fronting is widely used by malware to evade network-based detection, it will likely frustrate app developers who use it to get around internet censorship. From the report: First spotted by Tor developers on April 13th, the change has been rolling out across Google services and threatens to disrupt services for a number of anti-censorship tools, including Signal, GreatFire.org and Psiphon's VPN services. Reached by The Verge, Google said the changes were the result of a long-planned network update. "Domain fronting has never been a supported feature at Google," a company representative said, "but until recently it worked because of a quirk of our software stack. We're constantly evolving our network, and as part of a planned software update, domain fronting no longer works. We don't have any plans to offer it as a feature."
Domain-fronting allowed developers to use Google as a proxy, forwarding traffic to their own servers through a Google.com domain. That was particularly important for evading state-level censorship, which might try to block all the traffic sent to a given service. As long as the service was using domain-fronting, all the in-country data requests would appear as if they were headed for Google.com, with encryption preventing censors from digging any deeper. We do not yet know exactly why and when Google is shutting down the practice, but will update this post once we learn more.
Domain-fronting allowed developers to use Google as a proxy, forwarding traffic to their own servers through a Google.com domain. That was particularly important for evading state-level censorship, which might try to block all the traffic sent to a given service. As long as the service was using domain-fronting, all the in-country data requests would appear as if they were headed for Google.com, with encryption preventing censors from digging any deeper. We do not yet know exactly why and when Google is shutting down the practice, but will update this post once we learn more.
I think G doesn't really mind censorship these days. After all, they seem to be fans of it themselves.
But I need google domain fronting for my youtube comic con channel click-bot to work. Otherwise, youtube doesn't count the click-bot views!
What am I going to do? Any slashdotter can suggest an alternative for me?
Thanks in advance!
https://xkcd.com/1172/
The reason is precisely as Google has stated it. Domain fronting is a hack and arguably a symptom of a security weak point; neither should be relied upon in the long run.
~ C.
If they want to be able to operate in the EU, they can't have any "right to have your illegal activities forgotton" data relayed through their servers.
Domain fronting is a case of "just because you can do something, doesn't mean you should."
Domain-Fronting was a good idea with a huge potential for abuse.
VPNs and TOR are the answer to getting around blocks. While you are at it, switch your DNS to 1.1.1.1
The real answer to our problem is to kick China and Russia off the Internet until they learn how to behave.
i.e. the service Telegram is using to evade Russia.
If there's any doubt that Google would stand up to Russia, take a look here. Russia blocks Google, Google pulls the service.
And can you blame them?
As a corporation, defending freedom is not profitable, and as people, Sergey Mikhaylovich Brin has family in Russia, family with balconies and door handles.
So they comply with Putin, just as Trump did in cancelling the new Russian sanctions.
After all, they seem to be fans of it themselves.
As are most of the voters. This is one big social problem that needs a technical solution. Whether one is possible doesn't matter, we have to try. We cannot let fascists decide what we can see and hear. Remember, *when you let them, you help them*.
Even G can't risk going down because a government decides to block IPs of a fronted service. Like Russia today and AWS !?
Or to take a more serious example of a censurious environment, American college campuses.
Because we can all tell that it's just APK shitposting and then responding to himself with his customary "factual and true", perhaps?
Il n'y a pas de Planet B.
Comment removed based on user account deletion
That's right, in the EU we believe that people should be given a second chance to learn from their mistakes and lead a normal life after prison.
To me, Signal is definitely, terribly, unperfect, but it is the single and only *open-source* app allowing end-to-end encryption for short messaging (and, sometimes, phone calls).
I use it daily.
How does this Google move hits Signal?
Herve S.
I think G doesn't really mind censorship these days. After all, they seem to be fans of it themselves.
Sorry, I was going to reply to your comment, but it mysteriously no longer showed up in a search.
Quiz: A client wants to connect to a remote endpoint without a passive network observer being able to learn the identity of the endpoint. Is this "malware talking to the control server" or "banned application attempting to evade ISP-enforced censorship"?
Well obviously it's neither/both because there is no damned difference. As far as the transport layer is concerned, an application is an application. If you make it a desirable property that clients can conceal the true identity of the remote endpoint then you sweep in both.
Maybe this will change if we get adoption of RFC 3514 though.
Not sure about "domain fronting", but this little hack still works:
https://translate.google.com/translate?sl=fr&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=https%3A%2F%2Fyro.slashdot.org%2Fstory%2F18%2F04%2F18%2F2338210%2Fgoogle-is-shuttering-domain-fronting-creating-a-big-problem-for-anti-censorship-tools&edit-text=
Might makes right irrelevant.
Nothing wrong with that, the shit they don't want you to remember isn't worth remembering anyway
Yeah, like the Armenian Genocide by Turkey, or the Holocaust by Germany.
These two examples are exactly why you don't need a government tell you what you can and can't remember. But then again, the EUSSR has been on the slippery slope of censorship for a loooong time now. It started with the children. Then the terrorists. Then the poor ex-cons. What's next, offensive tweets?
I'm not a complete idiot... Some parts are missing.