[tor-bugs] #24367 [Core Tor/Tor]: Changing pluggable transports (during start-up) in Tor Browser is broken
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Dec 13 16:57:13 UTC 2017
#24367: Changing pluggable transports (during start-up) in Tor Browser is broken
-------------------------------------------------+-------------------------
Reporter: gk | Owner: (none)
Type: defect | Status:
| needs_information
Priority: Medium | Milestone: Tor:
| 0.3.2.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.0.1-alpha
Severity: Normal | Resolution:
Keywords: 030-backport, 031-backport, | Actual Points:
regression, tor-bridge-client, s8-errors, |
tbb-wants |
Parent ID: | Points: 0.5
Reviewer: | Sponsor:
| Sponsor8-can
-------------------------------------------------+-------------------------
Comment (by nickm):
I've been staring at the logs, and I have a new idea:
{{{
Nov 22 11:37:06.000 [info] TLS error while handshaking with [scrubbed]:
wrong version number (in SSL routines:ssl3_get_record:SSLv3/TLS write
client hello)
}}}
This is an error I might expect to see if we had a mismatched pluggable
transport: if we weren't using one when we were supposed to, or if we were
using the wrong one and the transport didn't notice.
I've made a new branch `ideas_for_24367` to try to track down this
possibility. It doesn't make any changes: it just adds new logs to 0.3.2
to keep track of our transport plans, and the bridge addresses we think
our guards have. Could you generate info-level logs for the failing case
using this branch?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24367#comment:27>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list