[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2106 [Tor Client]: Controller can't unset httpsproxy if it doesn't resolve
#2106: Controller can't unset httpsproxy if it doesn't resolve
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: major | Milestone: Tor: 0.2.3.x-final
Component: Tor Client | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Changes (by arma):
* cc: chiiph, erinn (added)
Comment:
Here's another instance:
1) Download vanilla TBB. Run it. Click sharing, become a relay, click ok.
Great. Exit TBB.
2) nc -l -p 9001 (or whatever port your relay wants to use).
3) Run TBB again. It will launch Tor, which will try to bind to the port,
and fail. Vidalia will pop up windows about not being able to connect to
Tor. Fine. Check the advanced message log, see that it's because Tor
couldn't bind to 9001. Click sharing, become a client, click ok. Exit and
restart TBB. Same Vidalia popups, except now when you click sharing you're
already a client! Vidalia thinks you're a client but Tor thinks you're a
relay. Vidalia can't start Tor to change Tor's mind. You have to rm -rf
the whole thing and start over.
This just bit a user on #tor.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2106#comment:3>
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