[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #13788 [Tor Browser]: Meek bridges don't work in TB 4.5alpha1
#13788: Meek bridges don't work in TB 4.5alpha1
-----------------------------+----------------------
Reporter: cypherpunks | Owner: tbb-team
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor Browser | Version:
Resolution: | Keywords: meek
Actual Points: | Parent ID:
Points: |
-----------------------------+----------------------
Comment (by gk):
Replying to [comment:14 arthuredelstein]:
> Replying to [comment:13 dcf]:
> [snip]
> > It seems that previously the code used `!mProxyHost.IsEmpty()` as the
signal for a proxy being set, not merely `mProxyHost` being true. Maybe
that old condition should be restored?
> > https://gitweb.torproject.org/tor-
browser.git/diff/netwerk/base/src/nsSocketTransport2.h?h=tor-
browser-31.2.0esr-4.5-1&id=e0eaf6b471ae3bbc06066232a00f3b27c2bedeee
>
> I'm posting a fixup here that simplifies that patch (e0eaf6b4) and
restores the use of `!mProxyHost.IsEmpty()` in nsSocketTransport2.*. I did
this work in trying to get the patch to land in mozilla-central (still
working on that). The patch works for domain isolation, but I haven't had
a chance to test it with meek. If anyone wants to give it a try, let me
know if this helps.
No, alas not. Meek is still not working for me if applying the patch.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13788#comment:18>
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