Opened 7 years ago

Closed 12 months ago

#4823 closed defect (wontfix)

Please use local user's path when starting Tor

Reported by: dererk Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version: Vidalia: 0.2.15
Severity: Normal Keywords: archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Vidalia is configured to use a certain controlsocket, and it will use it, either to connect to a currently running Tor instance, or to start a new one using that specific value.

This presents a few cases in which you couldn't and also shouldn't do that, one of them might be this:

You are already running a Tor instance which you are not supposed to hook against to. This is the case of a multiuser system in which many different users will start their own Tor instances, i.e, for privacy reasons. In this case, permissions wont allow Vidalia to hang to that controlsocket, and it will simply fail to start.

One possible way to avoid this could be as simple as:

  • If you couldn't connect to a running Tor instance (because foobar reasons), simply start a new one, but override controlsocket to, for example, ~/.tor/control/socket.

Bare in mind that the directory containing the socket should be 0700, otherwise Tor will fail to start.

Child Tickets

Change History (7)

comment:1 Changed 7 years ago by dererk

Owner: set to chiiph
Status: newassigned

comment:2 Changed 7 years ago by dererk

See a temporal workaround to this issue at README.Debian (/usr/share/doc/vidalia/README.Debian.gz)

comment:3 Changed 7 years ago by arma

Component: - Select a componentVidalia

comment:4 Changed 7 years ago by chiiph

I'm trying to figure out the best way of solving this, and a couple of issues come to mind:

  • What if the user is actually trying to connect to a running tor but she's failing to configure certain thing properly?
  • Would this be done only in the case of using ControlSocket?

But I think the stronger point here is how to differentiate between a user that has the problem you describe and the one that is just missing some config and should try again.

comment:5 Changed 7 years ago by arma

See also ticket #4805, which is a bunch of unhappy users apparently experiencing this bug.

comment:6 Changed 19 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:7 Changed 12 months ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: assignedclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.