[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tor-talk] Meek Problems
I actually figured out the problem a couple of days ago. The sensor
is changing the Google.com URL to something odd that I think may
affect the TLS. So instead of fronting www.google.com, I told Tor
Browser to front gmail.com and it worked.
Thanks for the information,
On 10/21/15, Dominik Ungar <firstname.lastname@example.org> wrote:
> Hi Justin,
> I just tried connecting with meek-google and it works fine so I would
> assume that your IT department has a proxy running which is filtering some
> URLs. Try to connect with meek-amazon, works fine on my schools network.
> Best Regards
> Am 19.10.2015 03:22 schrieb "Justin" <email@example.com>:
>> When I connect to Tor at school without bridges, it works fine. The issue
>> is that my IT department has a DPI unit that can tell I’m using Tor, so I
>> tried using Meek. When Tor starts, it boot straps to 10%, then stops.
>> When I click Open Settings, it says Tor failed to establish an encrypted
>> directory connection. Somehow, Meek is being broken by the sensor. I
>> thought the sensor might be doing a man in the middle on Google, but when
>> load the web site, I don’t get any MITM warnings. OBFS 3 and 4 and
>> Scramblesuit work just fine, along with regular Tor. My question to you
>> guys is, what would the filter be doing to break Meek?
>> The funny thing is that I don’t think it’s breaking Meek on purpose.
>> tor-talk mailing list - firstname.lastname@example.org
>> To unsubscribe or change other settings go to
> tor-talk mailing list - email@example.com
> To unsubscribe or change other settings go to
tor-talk mailing list - firstname.lastname@example.org
To unsubscribe or change other settings go to