Opened 10 years ago

Closed 2 years ago

Last modified 19 months ago

#2308 closed enhancement (wontfix)

Need instructions for using Vidalia when Tor is started at boot

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


First off, thank your for the great tools /w the tor & the vidalia.

I'm running the tor on FC14 & all is working very well. My tor is setup to start at bootup as a daemon. So the nice vidalia tools do not seem to be able to connect to the tor service now since the tor is no longer started by the vidalia.. I'm hoping that future releases will be able to monitor the tor status with vidalia even when it's not started in the vidalia.. It will be very cool.

Thank you very much for your time.

Child Tickets

Change History (10)

comment:1 Changed 10 years ago by rransom

Resolution: implemented
Status: newclosed

This is already possible. Look up the CookieAuthentication, CookieAuthFile, and CookieAuthFileGroupReadable torrc options in the Tor man page.

comment:2 Changed 10 years ago by chiiph

Also check if you have ControPort configured in your torrc, otherwise Vidalia won't be able con communicate with Tor.

comment:3 Changed 10 years ago by arma

Resolution: implemented
Status: closedreopened

comment:4 Changed 10 years ago by arma

Sounds like we should write this out as a faq entry, since it's non-obvious what to do when you're a unix tor user and want to add Vidalia to the mix.

(In short, you've got two choices. You can either disable Tor's start-at-boot, and let Vidalia launch Tor for you; or you can configure your Tor with a controlport and a HashedControlPassword, and then configure your Vidalia to know that password. There's a third choice, which involves using cookie authentication rather than password authentication, but that's probably best left to package maintainers rather than ordinary users, since I'd worry that it's too easy to screw up the file permissions.)

comment:5 Changed 10 years ago by atagar

Why not just have Vidalia attempt cookie authentication and no-auth when the password attempt fails? The control port provides the location of the cookie file when you query PROTOCOLINFO (when 'AUTH METHODS=COOKIE' there's a 'COOKIEFILE="/path/to/cookie" entry). This is fetched by TorCtl at:

The only times that Vidalia should fail to connect is when (a) the existing Tor instance has a controller password that Vidalia doesn't know or (b) Vidalia doesn't have permissions to read the cookie file.

Cheers! -Damian

comment:6 Changed 10 years ago by ladetor


Thank you all for the generous helps!

For other rookies like me, here is what I did step-by-step:

  1. Manually generate a HashControlPassword (e.g. tor --hash-password thekeeeeeeeey)
  2. use the hash in the /etc/tor/torrc
  3. turnoff the random generate password in vidalia
  4. use "thekeeeeeeeey" instead. 

& voila it works!

Also, I'd chmod o-rwx on the /etc/tor/torrc & the vidalia.conf just to be safe.

comment:7 Changed 10 years ago by arma

Summary: Cannot use the vidalia tools if started the tor as service at bootNeed instructions for using Vidalia when Tor is started at boot

comment:8 Changed 9 years ago by chiiph

I wonder if Fedora is using the ControlSocket stuff that was added a while ago.
I think we can consider this issue solved for Debian.

comment:9 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:10 Changed 2 years ago by teor

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

Close all tickets in archived components

Note: See TracTickets for help on using tickets.