Re: [tor-talk] Setting up Tor on Ubuntu

[Simon Brereton <simon.brereton@xxxxxxxxxxxxxx>]

On 22 March 2012 00:51, Dererk <dererk@xxxxxxxxxxxx> wrote:
> On 21/03/12 00:28, Simon Brereton wrote:
>> Hi
>>
>> Let me apologise at the outset for ignoring the TBB. ÂI plan on doing
>> so later, but as this is my first experiment with Tor, I would like to
>> try and educate myself and that means doing things the hard way.
>> Sadly, the hard way isn't working.
> [snip]
>> So, then I installed vidalia and privoxy. ÂOnce I stopped tor (sudo
>> /etc/init.d/tor stop) and started vidalia, I get the control panel up.
>>
>> If I start tor from the control panel, I get..
>>
>> Vidalia detectd that the Tor software exited unexpectedly.
>>
>> The log file says:
>>
>> Mar 20 22:58:45.620 [Warning] /var/run/tor is not owned by this user
>> (spb, 1000) but by debian-tor (116). Perhaps you are running Tor as
>> the wrong user?
> You could implement any approach present at the package documentation.
>
> Quoting:
>
> Â Â The 'But...'
> Â Â =======
>
> Â Â On the other hand, there could be a few situations in which you
> Â Âwont be able
> Â Â Âto use this configuration profile, some of them being:
>
> Â Â Â- You couldn't convince an admin to add you into the list of local
> Â Âsystem
> Â Â Â Âusers allowed to control Tor
> Â Â Â- The Tor instance you're willing to control runs on a remote host
> Â Â Â- Some old manuscripts have recently revealed vulnerabilities on the
> Â Â Â Âunixsocket implementation, or simply you just don't wish to use
> Â Âit because
> Â Â Â Âyou dislike the word 'unix' on 'unixsocket'.
>
>
> Â Â In this cases, or whichever ones you may find, you can still make
> Â Âuse any of
> Â Â Âthe following alternatives:
>
> Â Â Â1. If facing a local Tor daemon situation in which you are unable
> Â Âto connect
> Â Â Â Â for some reason to the system-wide Tor's Control Socket (as the
> Â Âexample
> Â Â Â Â explained below), you can still launch a personal Tor session
> Â Âand manually
> Â Â Â Â configure Vidalia to use it.
>
> Â Â Â2. Enable Tor's ControlPort and enable CookieAuthentication in
> Â ÂTor's config,
> Â Â Â Âthen grab the cookie file from /var/lib/tor/control_auth_cookie,
> Â Âprofit!
>
> Â Â Â3. Enable Tor's ControlPort, get a hashed password at 'tor
> Â Â--hash-password',
> Â Â Â Âload back the output into the HashedControlPassword Tor's config
> Â Âfield,
> Â Â Â Âprofit!
>
>
> Detailed explanation to be found on your system at:
> /usr/share/doc/vidalia/README.Debian.gz


Doh!  I thought this had been done as part of the set-up (I thought I
had seen this done). I'll do that.

Cheers

Simon
_______________________________________________
tor-talk mailing list
tor-talk@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk