#24432: The meek<->moat tunneling isn't set up correctly ----------------------------------+-------------------------- Reporter: isis | Owner: isis Type: defect | Status: reopened Priority: High | Milestone: Component: Obfuscation/BridgeDB | Version: Severity: Normal | Resolution: Keywords: moat bridgedb-dist | Actual Points: Parent ID: #24689 | Points: 2 Reviewer: | Sponsor: SponsorM ----------------------------------+--------------------------
Comment (by mcs): Replying to [comment:20 gk]: > Wow, thanks a lot for this analysis. Let me skip over it to jump to your conclusions part... Indeed, thanks! David, you are my hero. > Given that the analysis shows that at least part of the problem is due to the patch itself and how it interacts with the other Firefox networking code I think we should back it out and rewrite it if we want to keep it. We actually have #19910 for that and I think the OP describes a scenario that is compatible with the one you are seeing. Let's do it! Kathy and I wrestled with the SOCKS optimistic data patch once before. It just seems too fragile given the way the networking and TLS code is layered inside Firefox. The only thing I don't know is whether removing it will impact web page load times in a significant way. Another approach would be add an option to disable the SOCKS optimistic data feature on a per-connection basis, which would allow Tor Launcher to disable that option when it is using meek directly. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24432#comment:21> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs