I managed to get some information on why meek-google got suspended on App Engine. There was a botnet that used Tor and the public meek instance for command communication. They shut it down for that reason. I still haven't gotten any kind of official communication from Google Cloud Platform.
I wrote a guide on how people can set up their own personal instance. https://lists.torproject.org/pipermail/tor-talk/2016-June/041699.html I figure the botnet risk is far less this way, without a single central service to freeload off of. Though of course far fewer people will be able to follow these steps than were able to use a default configuration.
Because I can't see just setting up a new account under the circumstances, I'm planning to ask the Tor Browser devs to remove the non-functional meek-google option.
On Thu, 30 Jun 2016 14:35:31 -0700 David Fifield david@bamsoftware.com wrote:
I managed to get some information on why meek-google got suspended on App Engine. There was a botnet that used Tor and the public meek instance for command communication. They shut it down for that reason. I still haven't gotten any kind of official communication from Google Cloud Platform.
I wonder if it's worth figuring out how to integrate "clicking on street signs" or whatever for the public meek instances...
Regards,
On 06/30/2016 05:35 PM, David Fifield wrote:
I managed to get some information on why meek-google got suspended on App Engine. There was a botnet that used Tor and the public meek instance for command communication. They shut it down for that reason. I still haven't gotten any kind of official communication from Google Cloud Platform.
David, thank you for your private communication regarding this issue. I'm sad to see that it's shut down but I understand Google's reasoning. Hopefully they will communicate more details to you.
It's been a pleasure and an honor to run the backend server for you for over a year now. I am certain that we helped thousands of people in censored countries. Meek-google has also proven helpful to me as well. Please let me know if I can assist you with any more infrastructure in the future.
I managed to get some information on why meek-google got suspended on App Engine. There was a botnet that used Tor and the public meek instance for command communication. They shut it down for that reason.
My condolences. Onion.link ran into this problem when attempting hosting at universities (Caltech, MIT) as well as major CDNs (Cloudflare, etc.) I never found a way around it. If you find one please share with the world.
-V
On Fri, Jul 1, 2016 at 5:35 AM, David Fifield david@bamsoftware.com wrote:
I managed to get some information on why meek-google got suspended on App Engine. There was a botnet that used Tor and the public meek instance for command communication. They shut it down for that reason. I still haven't gotten any kind of official communication from Google Cloud Platform.
I wrote a guide on how people can set up their own personal instance. https://lists.torproject.org/pipermail/tor-talk/2016-June/041699.html I figure the botnet risk is far less this way, without a single central service to freeload off of. Though of course far fewer people will be able to follow these steps than were able to use a default configuration.
Because I can't see just setting up a new account under the circumstances, I'm planning to ask the Tor Browser devs to remove the non-functional meek-google option. _______________________________________________ tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
tor-project@lists.torproject.org
-
David Fifield -
Jesse V -
Virgil Griffith -
Yawning Angel