[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2357 [Tor Bridge]: ReachableAddresses ignored when playing with bridges using Vidalia
#2357: ReachableAddresses ignored when playing with bridges using Vidalia
------------------------+---------------------------------------------------
Reporter: anonym | Owner: arma
Type: defect | Status: assigned
Priority: normal | Milestone: Tor: 0.2.2.x-final
Component: Tor Bridge | Version: Tor: 0.2.1.26
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by anonym):
Replying to [comment:4 arma]:
> Replying to [ticket:2357 anonym]:
> > 3. I start Vidalia and add a bridge. Tor immediately bootstraps and
all connections to the Tor network are made through the bridge (verified
with packet sniffer) as expected (except that the bridge connection is
exempt from !ReachableAddresses, see ticket #2356).
>
> See my explanation on #2356: when you click 'ok' from Vidalia, Vidalia
sets your ReachableAddresses as well as your Bridges, to the settings
you've configured with Vidalia.
Yup. That's a game changer, so I believe this bug is invalid.
> > 4. I restart Tor. Tor hangs on "Bootstrapping 85%" according to the
log, accompanied by the notices:
> >
> > Notice: no known bridge descriptors running yet; stalling
> >
> > and
> >
> > Notice: Our directory information is no longer up-to-date
> > enough to build circuits: No live bridge descriptors.
> >
> > What's Tor's problem with the bridge (I have verified that the bridge
works on another system)?
>
> How did you restart Tor? Presumably from inside Vidalia, by clicking
'stop tor' and 'start tor'? Is your Vidalia/Tor configuration such that
when you finished step 3, it overwrite Tor's torrc file? If yes, your
ReachableAddresses line should be gone. If no, Vidalia remembered the
changes it tried to get your Tor to saveconf, and applied them anew the
next time you asked it to start Tor.
I always run Tor as a system-wide instance and only let Vidalia control it
through the control port. When I start/stop Tor I do it with the init
script, and I always (by necessity) do that before I start Vidalia.
Vidalia is run by a normal user, and torrc is owned by root, so Vidalia
can't change it.
Case closed I think. As I said in #2356, I worked under faulty assumptions
on how Vidalia deals with options in torrc. I guess Vidalia is mostly
designed for the case when it starts/stops the Tor process and thus has
full control/ownership of it and torrc, and that there are some
inconsistencies w.r.t. importing settings from torrc when handling a
system instance (as in the Tails case).
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2357#comment:6>
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