[tbb-bugs] #22429 [Applications/Tor Browser]: bridge: Add Lisbeth IPv6 address

[Tor Bug Tracker & Wiki]

#22429: bridge: Add Lisbeth IPv6 address
-----------------------------------------------+--------------------------
 Reporter:  dgoulet                            |          Owner:  tbb-team
     Type:  enhancement                        |         Status:  closed
 Priority:  Medium                             |      Milestone:
Component:  Applications/Tor Browser           |        Version:
 Severity:  Normal                             |     Resolution:  fixed
 Keywords:  tbb-bridges TorBrowserTeam201706R  |  Actual Points:
Parent ID:                                     |         Points:
 Reviewer:                                     |        Sponsor:
-----------------------------------------------+--------------------------
Changes (by gk):

 * status:  needs_review => closed
 * resolution:   => fixed


Comment:

 Replying to [comment:3 dcf]:
 > Here is a patch. I tested the bridge line by itself in a torrc file, but
 I wasn't able to test it in Tor Browser on an IPv6-capable system.
 >
 > When Tor Browser tries to use the bridge line on an IPv4-only system,
 this is what appears in the log:
 > {{{
 > 06/01/2017 13:06:18.700 [NOTICE] DisableNetwork is set. Tor will not
 make or accept non-control network connections. Shutting down all existing
 connections.
 > 06/01/2017 13:06:18.700 [NOTICE] Opening Socks listener on
 127.0.0.1:9150
 > 06/01/2017 13:06:20.600 [NOTICE] Bootstrapped 5%: Connecting to
 directory server
 > 06/01/2017 13:06:20.600 [NOTICE] Bootstrapped 10%: Finishing handshake
 with directory server
 > 06/01/2017 13:06:20.600 [WARN] Proxy Client: unable to connect to
 2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
 > 06/01/2017 13:06:25.400 [NOTICE] Closing no-longer-configured Socks
 listener on 127.0.0.1:9150
 > 06/01/2017 13:06:25.400 [NOTICE] DisableNetwork is set. Tor will not
 make or accept non-control network connections. Shutting down all existing
 connections.
 > 06/01/2017 13:06:25.400 [NOTICE] Closing old Socks listener on
 127.0.0.1:9150
 > }}}

 Hrm. That's not good. I assume Tor Browser is randomly choosing one bridge
 the next time it starts (again) but we should be smarter here than making
 the user believe Tor Browser is broken. dcf: Do you know whether there is
 already a ticket anywhere for this issue?

 Picked this up for now on `master` and `maint-7.0` (commit
 6dbe2e65a8d5822d024669e90d7f920b453adce4 and
 94947a1c2333c4dcf0a0bf8af6228aceaf437ad2).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22429#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online