[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #25875 [Obfuscation/meek]: Azure meek bridge bootstrap fails without meek-client-torbrowser proxy
#25875: Azure meek bridge bootstrap fails without meek-client-torbrowser proxy
------------------------------+-------------------------------
Reporter: habib | Owner: dcf
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Obfuscation/meek | Version: Tor: 0.3.2.10
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
------------------------------+-------------------------------
Comment (by dcf):
Replying to [comment:3 habib]:
> Thanks for the quick reply, my meek-client.log:
> {{{
> meek-client + azure:
> 2018/04/21 00:23:57 listening on 127.0.0.1:61991
> 2018/04/21 00:24:00 status code was 411, not 200; trying again after 30
seconds (9)
> 2018/04/21 00:25:00 error in handling request: stream error: stream ID
5; PROTOCOL_ERROR
> 2018/04/21 00:25:32 error in handling request: stream error: stream ID
9; PROTOCOL_ERROR
> }}}
Aha, this is #22865. Status code 411 is "length required". This problem
was already fixed in meek 0.28, but it looks like Tor Browser is still
using meek 0.25.
Unfortunately you won't be able to use the meek-client you have, until I
ask to have meek upgraded in Tor Browser. If you cannot wait for another
Tor Browser release, you can compile meek-client yourself. It is not
''very'' difficult, but you will need to download the Go compiler:
https://golang.org/dl/.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25875#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs