I hope the “Network Forum” is the right place to ask this question.
All together I am quite happy with the new release 11.2 of Opensuse, and if I could solve the following issue everything would be perfect!
I installed the latest Tor package from the Packman Repo:
tor-0.2.1.20-1.pm.1.1.x86_64
and additionally the Privoxy package frpm the official Opensuse Repo:
privoxy-3.0.13.90.1-4.1.x86_64
the I went in
/etc/tor/
and copied the torrc.sample to have a valid torrc file:
cp torrc.sample torrc
after I configured /etc/privoxy/config
vi /etc/privoxy/config
and changed
To chain Privoxy and Tor, both running on the same system,
you would use something like:
forward-socks5 / 127.0.0.1:9050 .
to
forward-socks5 / 127.0.0.1:9050
as I m used to!
If I try now to start tor as a normal user from a terminal I get this:
Dec 02 16:17:05.377 [notice] Tor v0.2.1.20. This is experimental software. Do not rely on it for strong anonymity. (Running on Linux x86_64)
Dec 02 16:17:05.378 [notice] Initialized libevent version 1.4.9-stable using method epoll. Good.
Dec 02 16:17:05.378 [notice] Opening Socks listener on 127.0.0.1:9050
Dec 02 16:17:05.398 [notice] Parsing GEOIP file.
Dec 02 16:17:05.606 [notice] No current certificate known for authority moria1; launching request.
Dec 02 16:17:05.606 [notice] No current certificate known for authority tor26; launching request.
Dec 02 16:17:05.606 [notice] No current certificate known for authority dizum; launching request.
Dec 02 16:17:05.606 [notice] No current certificate known for authority ides; launching request.
Dec 02 16:17:05.606 [notice] No current certificate known for authority gabelmoo; launching request.
Dec 02 16:17:05.606 [notice] No current certificate known for authority dannenberg; launching request.
Dec 02 16:17:05.606 [notice] No current certificate known for authority urras; launching request.
Dec 02 16:17:05.606 [notice] Bootstrapped 5%: Connecting to directory server.
Dec 02 16:17:05.606 [notice] I learned some more directory information, but not enough to build a circuit: We have no network-status consensus.
Dec 02 16:17:05.845 [notice] Bootstrapped 10%: Finishing handshake with directory server.
Dec 02 16:17:06.516 [warn] TLS error: unexpected close while renegotiating
Dec 02 16:17:06.516 [notice] No current certificate known for authority moria1; launching request.
Dec 02 16:17:06.516 [notice] No current certificate known for authority tor26; launching request.
Dec 02 16:17:06.516 [notice] No current certificate known for authority dizum; launching request.
Dec 02 16:17:06.516 [notice] No current certificate known for authority ides; launching request.
Dec 02 16:17:06.516 [notice] No current certificate known for authority gabelmoo; launching request.
Dec 02 16:17:06.516 [notice] No current certificate known for authority dannenberg; launching request.
Dec 02 16:17:06.516 [notice] No current certificate known for authority urras; launching request.
Dec 02 16:17:07.016 [warn] TLS error: unexpected close while renegotiating
Dec 02 16:17:07.086 [warn] TLS error: unexpected close while renegotiating
why do you always need to quote a post? This is very annoying, especially if the OPs post is pretty long and you quote it. You always seem to do it… grrrrr
first, i was never able to make the privoxy package actually work from the 11.2 repo, and used another release.
second, if you research this, i think you will find that the recent openssl update to mitigate the “man-in-the-middle” exploit makes tor almost unusable unless you use the current svn 0.2.2.6alpha version.
the “mitm” vunerability doesn’t effect the security of tor due to the way it establishes ssl connections, but since the new openssl patch prevents “re-negotiation”, tor is put in handcuffs looking for routes. The alpha version sidesteps this issue.
I’ve done this it works fine as j_xavier said that version but I found it on the OBS, I also used the privoxy from the standard repos and it works fine.
I had the same problem with some “looks like a v2 handshake” sh*t in logs…
I deleted old tor and tried this alpha 0.2.2 Software.openSUSE.org but it did not help.
So I installed from sources from tor site and all work now rotfl!
BTW be careful, there is no /etc/init.d/tor script and you should start it simply “tor” (I did it from root cause otherwise he did not have some permissions).
Also old config didn’t work so use the new one.
Just copy torrc.sample to torrc as it is almost always enough…
tork still is very useful to me despite the fact that kde applications launcher “Anonymize” tab panel cannot start kde4 applications.
altering the network/proxy settings of the application to point to privoxy or tor depending on your needs works for apps that have this configuring ability.
but more importantly, once you get the application using tor, having tork running gives you more control over all the tor connections.
it’s my understanding that a kde4 Tork is being planned, but there is no release date.
Tork does have a problem with those functions now, i spoke with the developer on irc.oftc.net months ago.
for me it was crashing when sorting servers, turns out the huge increase in tor servers (2900 online at this moment) is more than Tork can handle, and crashes every time it tries to sort/parse them.
i’ll see if i can find out any more info, but for now that feature is broken.
