При первом запуске vidalia Tor выдает предупреждения

Update март 2015: Уже более года Vidalia можно не устанавливать. Инсталлировать Tor-Browser стало проще. Новые инструкции и ссылки в комментариях к посту. Далее текст првоначального поста.
Depricated: Здесь мы решаем проблемы с утановкой vidalia и TorBrowser на Debian. О настройке vidalia есть мануал c картинками на сайте
После установки в Debian не сразу нашел луковицу(иконнку программы) в трее наверху, но обнаружил "vidalia" в разделе меню "Intenet". При открытии программа выдала предупреждение и попросила прочитаь лог:

In []:

Apr 04 14:21:47.899 [Notice] Tor v0.2.3.25 (git-3fed5eb096d2d187) running on Linux.
Apr 04 14:21:47.899 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 04 14:21:47.902 [Notice] Read configuration file "/home/kiss/.vidalia/torrc".
Apr 04 14:21:47.913 [Notice] Initialized libevent version 2.0.19-stable using method epoll (with changelist). Good.
Apr 04 14:21:47.914 [Notice] Opening Socks listener on 127.0.0.1:9050
Apr 04 14:21:47.914 [Warning] Directory /var/run/tor does not exist.
Apr 04 14:21:47.914 [Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
Apr 04 14:21:47.914 [Notice] Closing partially-constructed Socks listener on 127.0.0.1:9050
Apr 04 14:21:47.915 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Apr 04 14:21:47.915 [Error] Reading config failed--see warnings above.

In [2]:

!cat /home/kiss/.vidalia/torrc

Команда ничего не выдала, т.к. файл пустой.

In [1]:

!cat /etc/tor/torrc

## Configuration file for a typical Tor user

## Last updated 22 April 2012 for Tor 0.2.3.14-alpha.

## (may or may not work for much older or much newer versions of Tor.)

##

## Lines that begin with "## " try to explain what's going on. Lines

## that begin with just "#" are disabled commands: you can enable them

## by removing the "#" symbol.

##

## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,

## for more options you can use in this file.

##

## Tor will look for this file in various places based on your platform:

## https://www.torproject.org/docs/faq#torrc



## Tor opens a socks proxy on port 9050 by default -- even if you don't

## configure one below. Set "SocksPort 0" if you plan to run Tor only

## as a relay, and not make any local application connections yourself.

#SocksPort 9050 # Default: Bind to localhost:9050 for local connections.

#SocksPort 192.168.0.1:9100 # Bind to this adddress:port too.



## Entry policies to allow/deny SOCKS requests based on IP address.

## First entry that matches wins. If no SocksPolicy is set, we accept

## all (and only) requests that reach a SocksPort. Untrusted users who

## can access your SocksPort may be able to learn about the connections

## you make.

#SocksPolicy accept 192.168.0.0/16

#SocksPolicy reject *



## Logs go to stdout at level "notice" unless redirected by something

## else, like one of the below lines. You can have as many Log lines as

## you want.

##

## We advise using "notice" in most cases, since anything more verbose

## may provide sensitive information to an attacker who obtains the logs.

##

## Send all messages of level 'notice' or higher to /var/log/tor/notices.log

#Log notice file /var/log/tor/notices.log

## Send every possible message to /var/log/tor/debug.log

#Log debug file /var/log/tor/debug.log

## Use the system log instead of Tor's logfiles

#Log notice syslog

## To send all messages to stderr:

#Log debug stderr



## Uncomment this to start the process in the background... or use

## --runasdaemon 1 on the command line. This is ignored on Windows;

## see the FAQ entry if you want Tor to run as an NT service.

#RunAsDaemon 1



## The directory for keeping all the keys/etc. By default, we store

## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.

#DataDirectory /var/lib/tor



## The port on which Tor will listen for local connections from Tor

## controller applications, as documented in control-spec.txt.

#ControlPort 9051

## If you enable the controlport, be sure to enable one of these

## authentication methods, to prevent attackers from accessing it.

#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C

#CookieAuthentication 1



############### This section is just for location-hidden services ###



## Once you have configured a hidden service, you can look at the

## contents of the file ".../hidden_service/hostname" for the address

## to tell people.

##

## HiddenServicePort x y:z says to redirect requests on port x to the

## address y:z.



#HiddenServiceDir /var/lib/tor/hidden_service/

#HiddenServicePort 80 127.0.0.1:80



#HiddenServiceDir /var/lib/tor/other_hidden_service/

#HiddenServicePort 80 127.0.0.1:80

#HiddenServicePort 22 127.0.0.1:22



################ This section is just for relays #####################

#

## See https://www.torproject.org/docs/tor-doc-relay for details.



## Required: what port to advertise for incoming Tor connections.

#ORPort 9001

## If you want to listen on a port other than the one advertised in

## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as

## follows.  You'll need to do ipchains or other port forwarding

## yourself to make this work.

#ORPort 443 NoListen

#ORPort 127.0.0.1:9090 NoAdvertise



## The IP address or full DNS name for incoming connections to your

## relay. Leave commented out and Tor will guess.

#Address noname.example.com



## If you have multiple network interfaces, you can specify one for

## outgoing traffic to use.

# OutboundBindAddress 10.0.0.5



## A handle for your relay, so people don't have to refer to it by key.

#Nickname ididnteditheconfig



## Define these to limit how much relayed traffic you will allow. Your

## own traffic is still unthrottled. Note that RelayBandwidthRate must

## be at least 20 KB.

## Note that units for these config options are bytes per second, not bits

## per second, and that prefixes are binary prefixes, i.e. 2^10, 2^20, etc.

#RelayBandwidthRate 100 KB  # Throttle traffic to 100KB/s (800Kbps)

#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)



## Use these to restrict the maximum traffic per day, week, or month.

## Note that this threshold applies separately to sent and received bytes,

## not to their sum: setting "4 GB" may allow up to 8 GB total before

## hibernating.

##

## Set a maximum of 4 gigabytes each way per period.

#AccountingMax 4 GB

## Each period starts daily at midnight (AccountingMax is per day)

#AccountingStart day 00:00

## Each period starts on the 3rd of the month at 15:00 (AccountingMax

## is per month)

#AccountingStart month 3 15:00



## Contact info to be published in the directory, so we can contact you

## if your relay is misconfigured or something else goes wrong. Google

## indexes this, so spammers might also collect it.

#ContactInfo Random Person <nobody AT example dot com>

## You might also include your PGP or GPG fingerprint if you have one:

#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>



## Uncomment this to mirror directory information for others. Please do

## if you have enough bandwidth.

#DirPort 9030 # what port to advertise for directory connections

## If you want to listen on a port other than the one advertised in

## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as

## follows.  below too. You'll need to do ipchains or other port

## forwarding yourself to make this work.

#DirPort 80 NoListen

#DirPort 127.0.0.1:9091 NoAdvertise

## Uncomment to return an arbitrary blob of html on your DirPort. Now you

## can explain what Tor is if anybody wonders why your IP address is

## contacting them. See contrib/tor-exit-notice.html in Tor's source

## distribution for a sample.

#DirPortFrontPage /etc/tor/tor-exit-notice.html



## Uncomment this if you run more than one Tor relay, and add the identity

## key fingerprint of each Tor relay you control, even if they're on

## different networks. You declare it here so Tor clients can avoid

## using more than one of your relays in a single circuit. See

## https://www.torproject.org/docs/faq#MultipleRelays

## However, you should never include a bridge's fingerprint here, as it would

## break its concealability and potentionally reveal its IP/TCP address.

#MyFamily $keyid,$keyid,...



## A comma-separated list of exit policies. They're considered first

## to last, and the first match wins. If you want to _replace_

## the default exit policy, end this with either a reject *:* or an

## accept *:*. Otherwise, you're _augmenting_ (prepending to) the

## default exit policy. Leave commented to just use the default, which is

## described in the man page or at

## https://www.torproject.org/documentation.html

##

## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses

## for issues you might encounter if you use the default exit policy.

##

## If certain IPs and ports are blocked externally, e.g. by your firewall,

## you should update your exit policy to reflect this -- otherwise Tor

## users will be told that those destinations are down.

##

## For security, by default Tor rejects connections to private (local)

## networks, including to your public IP address. See the man page entry

## for ExitPolicyRejectPrivate if you want to allow "exit enclaving".

##

#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more

#ExitPolicy accept *:119 # accept nntp as well as default exit policy

#ExitPolicy reject *:* # no exits allowed



## Bridge relays (or "bridges") are Tor relays that aren't listed in the

## main directory. Since there is no complete public list of them, even an

## ISP that filters connections to all the known Tor relays probably

## won't be able to block all the bridges. Also, websites won't treat you

## differently because they won't know you're running Tor. If you can

## be a real relay, please do; but if not, be a bridge!

#BridgeRelay 1

## By default, Tor will advertise your bridge to users through various

## mechanisms like https://bridges.torproject.org/. If you want to run

## a private bridge, for example because you'll give out your bridge

## address manually to your friends, uncomment this line:

#PublishServerDescriptor 0

Пора подвести первые итоги. Согласно заверениям разработчиков, Tor должен и в первый ра запускаться сам... На Windows так и происходит... Попытка создать папки, которых нет Ticket... Кроме того, в фирменном руководстве написано Running the Tor client on Linux/BSD/Unix

In []:

Now you can run tor as 
src/or/tor, or you can run make install (as root if necessary) to install it into 
/usr/local/, and then you can start it just by running tor.

Tor comes configured as a client by default. It uses a built-in default configuration file, 
and most people won't need to change any of the settings. 
Tor is now installed. 

Решение найдено¶

Метод научного тыка торжествует. Первым делом я решил не менять hash пароль, как советовал в занудливом ролика пытливый kali пользователь, а просто перекинуть галочку с "Use Unix domain socket..." "Use TSP connection (control port)" и пришло счастье:

In []:

Apr 04 16:29:34.511 [Notice] Tor v0.2.3.25 (git-3fed5eb096d2d187) running on Linux.
Apr 04 16:29:34.512 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 04 16:29:34.512 [Notice] Read configuration file "/home/kiss/.vidalia/torrc".
Apr 04 16:29:34.513 [Notice] Initialized libevent version 2.0.19-stable using method epoll (with changelist). Good.
Apr 04 16:29:34.513 [Notice] Opening Socks listener on 127.0.0.1:9050
Apr 04 16:29:34.513 [Notice] Opening Control listener on 127.0.0.1:9051
Apr 04 16:29:34.521 [Notice] This version of OpenSSL has a known-good EVP counter-mode implementation. Using it.
Apr 04 16:29:34.611 [Notice] OpenSSL OpenSSL 1.0.1e 11 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Apr 04 16:29:34.643 [Notice] Reloaded microdescriptor cache.  Found 0 descriptors.
Apr 04 16:29:34.643 [Notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Apr 04 16:29:35.644 [Notice] Bootstrapped 5%: Connecting to directory server.
Apr 04 16:29:35.644 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 1 circuits open. I've sent 0 kB and received 0 kB.
Apr 04 16:29:35.715 [Notice] Bootstrapped 10%: Finishing handshake with directory server.
Apr 04 16:29:35.943 [Notice] Bootstrapped 15%: Establishing an encrypted directory connection.
Apr 04 16:29:36.193 [Notice] Bootstrapped 20%: Asking for networkstatus consensus.
Apr 04 16:29:36.268 [Notice] Bootstrapped 25%: Loading networkstatus consensus.
Apr 04 16:29:38.485 [Notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Apr 04 16:29:39.048 [Notice] Bootstrapped 40%: Loading authority key certs.
Apr 04 16:29:39.408 [Notice] Bootstrapped 45%: Asking for relay descriptors.
Apr 04 16:29:39.408 [Notice] I learned some more directory information, but not enough to build a circuit: We have only 0/5491 usable microdescriptors.
Apr 04 16:29:39.487 [Notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
Apr 04 16:29:49.780 [Notice] We now have enough directory information to build circuits.
Apr 04 16:29:49.781 [Notice] Bootstrapped 80%: Connecting to the Tor network.
Apr 04 16:29:49.869 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Apr 04 16:29:50.137 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
Apr 04 16:29:51.147 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 04 16:29:51.147 [Notice] Bootstrapped 100%: Done.

А этот безумный учил, что в конфигурационном файле надо найти строчку "#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C" и задать новый хэш (команда внизу).
Вот только она (эта строчка) у меня закомментирована (и у него вроде бы тоже была...), словом я себе показался очень умным, включив "Use TSP connection (control port)" , но ненадолго...
Мне ведь еще надо разобраться, что это я отключил... "Use Unix domain socket..." ...так что вот внизу задел на будущее

In []:

#!sudo /etc/unit.d/tor restart
#!tor --hash-password mypassword

Устанавливае браузер Tor !!! Do not unpack or run TBB as root !!!¶

Действуе по инструкции с сайта Tor Linux Instructions

In []:

cd /home/kiss/Desktop
# for 32-bit veersion 
tar -xvJf tor-browser-linux32-3.6-beta-1_en-US.tar.xz

In []:

Once that's done, switch to the Tor browser directory by running:
cd tor-browser_en-US

In []:

#To run the Tor Browser Bundle, execute the start-tor-browser script:
./start-tor-browser
#This will launch Tor Launcher and once that connects to Tor, it will launch Firefox. Do not unpack or run TBB as root.

In []:

kiss@kali:~/Desktop/tor-browser_en-US$ ./start-tor-browser

Launching Tor Browser Bundle for Linux in /home/kiss/Desktop/tor-browser_en-US
Apr 04 17:57:38.409 [notice] Tor v0.2.4.21 (git-0baa436a78840c20) running on Linux with Libevent 2.0.21-stable and OpenSSL 1.0.1f.
Apr 04 17:57:38.409 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 04 17:57:38.409 [notice] Read configuration file "/home/kiss/Desktop/tor-browser_en-US/Data/Tor/torrc-defaults".
Apr 04 17:57:38.409 [notice] Read configuration file "/home/kiss/Desktop/tor-browser_en-US/Data/Tor/torrc".
Apr 04 17:57:38.412 [notice] Opening Control listener on 127.0.0.1:9151
Apr 04 17:57:38.412 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
Apr 04 17:57:38.000 [notice] Pluggable transport proxy (fte exec ./Tor/PluggableTransports/fteproxy --managed) does not provide any needed transports and will not be launched.
Apr 04 17:57:38.000 [notice] Pluggable transport proxy (obfs2,obfs3 exec ./Tor/PluggableTransports/obfsproxy.bin managed) does not provide any needed transports and will not be launched.
Apr 04 17:57:38.000 [notice] Pluggable transport proxy (flashproxy exec ./Tor/PluggableTransports/flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched.
Apr 04 17:57:38.000 [notice] Parsing GEOIP IPv4 file /home/kiss/Desktop/tor-browser_en-US/Data/Tor/geoip.
Apr 04 17:57:38.000 [notice] New control connection opened.
Apr 04 17:57:38.000 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
Apr 04 17:57:38.000 [notice] Pluggable transport proxy (fte exec ./Tor/PluggableTransports/fteproxy --managed) does not provide any needed transports and will not be launched.
Apr 04 17:57:38.000 [notice] Pluggable transport proxy (obfs2,obfs3 exec ./Tor/PluggableTransports/obfsproxy.bin managed) does not provide any needed transports and will not be launched.
Apr 04 17:57:38.000 [notice] Pluggable transport proxy (flashproxy exec ./Tor/PluggableTransports/flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched.
Apr 04 17:57:38.000 [notice] New control connection opened.
Apr 04 17:57:54.000 [notice] Opening Socks listener on 127.0.0.1:9150
Apr 04 17:57:54.000 [notice] Pluggable transport proxy (fte exec ./Tor/PluggableTransports/fteproxy --managed) does not provide any needed transports and will not be launched.
Apr 04 17:57:54.000 [notice] Pluggable transport proxy (obfs2,obfs3 exec ./Tor/PluggableTransports/obfsproxy.bin managed) does not provide any needed transports and will not be launched.
Apr 04 17:57:54.000 [notice] Pluggable transport proxy (flashproxy exec ./Tor/PluggableTransports/flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched.
Apr 04 17:57:54.000 [notice] Renaming old configuration file to "/home/kiss/Desktop/tor-browser_en-US/Data/Tor/torrc.orig.1"
Apr 04 17:57:54.000 [notice] Bootstrapped 5%: Connecting to directory server.
Apr 04 17:57:54.000 [notice] Bootstrapped 10%: Finishing handshake with directory server.
Apr 04 17:57:55.000 [notice] Bootstrapped 15%: Establishing an encrypted directory connection.
Apr 04 17:57:56.000 [notice] Bootstrapped 20%: Asking for networkstatus consensus.
Apr 04 17:57:56.000 [notice] Bootstrapped 25%: Loading networkstatus consensus.
Apr 04 17:57:58.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Apr 04 17:57:59.000 [notice] Bootstrapped 40%: Loading authority key certs.
Apr 04 17:58:02.000 [notice] Bootstrapped 45%: Asking for relay descriptors.
Apr 04 17:58:02.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/5494, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw.)
Apr 04 17:58:02.000 [notice] Bootstrapped 50%: Loading relay descriptors.
Apr 04 17:58:03.000 [notice] Bootstrapped 51%: Loading relay descriptors.
Apr 04 17:58:03.000 [notice] Bootstrapped 53%: Loading relay descriptors.
Apr 04 17:58:03.000 [notice] Bootstrapped 55%: Loading relay descriptors.
Apr 04 17:58:04.000 [notice] Bootstrapped 57%: Loading relay descriptors.
Apr 04 17:58:04.000 [notice] Bootstrapped 59%: Loading relay descriptors.
Apr 04 17:58:04.000 [notice] Bootstrapped 61%: Loading relay descriptors.
Apr 04 17:58:13.000 [notice] Bootstrapped 63%: Loading relay descriptors.
Apr 04 17:58:13.000 [notice] Bootstrapped 65%: Loading relay descriptors.
Apr 04 17:58:13.000 [notice] Bootstrapped 67%: Loading relay descriptors.
Apr 04 17:58:13.000 [notice] Bootstrapped 69%: Loading relay descriptors.
Apr 04 17:58:13.000 [notice] Bootstrapped 71%: Loading relay descriptors.
Apr 04 17:58:13.000 [notice] Bootstrapped 72%: Loading relay descriptors.
Apr 04 17:58:13.000 [notice] Bootstrapped 74%: Loading relay descriptors.
Apr 04 17:58:14.000 [notice] Bootstrapped 76%: Loading relay descriptors.
Apr 04 17:58:14.000 [notice] Bootstrapped 78%: Loading relay descriptors.
Apr 04 17:58:23.000 [notice] We now have enough directory information to build circuits.
Apr 04 17:58:23.000 [notice] Bootstrapped 80%: Connecting to the Tor network.
Apr 04 17:58:23.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Apr 04 17:58:32.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 04 17:58:32.000 [notice] Bootstrapped 100%: Done.
0 migrated.
Apr 04 17:59:16.000 [notice] New control connection opened.
Could not check applicable rules for about:tor

Все работает, начинаем юзать... а с этой статьей заканчиваем.

Посты чуть ниже также могут вас заинтересовать