[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2355 [Tor Client]: change the meaning of UseBridges
#2355: change the meaning of UseBridges
------------------------------+---------------------------------------------
Reporter: anonym | Type: enhancement
Status: new | Priority: minor
Milestone: Tor: unspecified | Component: Tor Client
Version: | Keywords:
Points: | Parent:
------------------------------+---------------------------------------------
Comment(by anonym):
Replying to [comment:1 nickm]:
> It'd be nice to have a fix for this, though since it's pretty
specialized and there is (IIUC?) a working workaround, I'm not going to
call it urgent.
The workaround that was initially devised (and that I described to you
over IRC) was the following:
1) Add "ReachableAddresses reject *:*" to torrc
2) Start Tor
3) Let the user add bridges through vidalia
As detailed in bug #2357, this approach started out promising (bridges
seems to be exempt of rejection from ReachableAddresses so It Just
Works(TM) as soon as a bridge is added), but it breaks when Tor is
restarted.
The only alternative workaround I can think of is to add "UseBridges 1"
and a bogus bridge (e.g. "Bridge 127.0.0.1:12345") to torrc which will
prevent the Tor client from connecting to the Tor network until the user
adds a proper bridge through vidalia. This seems to work fine, but users
might get confused when they see that strange bridge turn up in vidalia.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2355#comment:2>
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