On Wed, May 11, 2016 at 11:16:28PM -0400, Blake Hadley wrote: > On 5/11/16 10:40 PM, David Fifield wrote: > > > Another solution is to change the front domain to something else, for > > exmaple using google.com instead of www.google.com. > Would it be feasible for a future release of meek to do this automatically? > Just cycle through subdomains till one works?
I don't think there's a point to doing that. Sure, it would temporarily mitigate this specific instance, but it's going back to the cat-and-mouse methods that I don't like. If the firewall vendor is okay with blocking all Firefox 38 users from www.google.com, they aren't going to have a problem with also blocking other domains. The weakness in this case, I think, was the obsolete TLS signature, not the domain name. -- tor-talk mailing list - [email protected] To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
