TorK - Anonymity Manager for KDE

Tracker: Bugs

5 Tork overrides torrc? - ID: 1958985

Last Update: Comment added ( nobody )

Details:

I am not sure if this is a bug or not but I am certain that I have no idea
what is going on. I have tork 0.28 and tor-0.2.0.25-rc. About a month ago
I setup my tor server as an exit for a period. I have since switched back
to a relay server (in Tork via the wizard). Even though I select
"Client/Relay" in Tork, the tor network still identifies me as an exit
server so I manually edited /usr/local/etc/tor/torrc so that it blocks all
exits. I restart tor via tork (still set for client/relay) and my tor
server STILL appears as an exit.

At this point I have to assume that somehow tork is overriding my torrc
still has tor run as an exit.

Submitted:

Praedor Tempus ( praedor ) - 2008-05-06 18:49

Priority:

Status:

Open

Resolution:

None

Assigned:

Nobody/Anonymous

Category:

None

Group:

None

Visibility:

Public

Comment ( 1 )

Date: 2008-05-06 20:57 Sender: nobody Logged In: NO Hi Praedor, First off, I don't doubt that you've encountered a bug of some sort here - either in code or usability. However, I can't replicate this problem at all. This is what I did: 1. Used the first run wizard to configure Tor as a client and server with default settings (i.e. exit). 2. Started Tor from Tork. 3. Confirmed that my server was running as an exit. It was. (see below for the commands to confirm this). 4. Stopped Tor via Tork. 5. Re-ran the wizard and this time selected client and relay server. 6. Started Tor from Tork. 7. Confirmed that my server was not running as an exit. To help get to the bottom of it you should disable authentication on Tor and follow the steps you are taking to use TorK to configure Tor as a relay, and use the following commands to establish how Tor is configured at each point: telnet localhost 9051 authenticate getconf exitpolicy An exitpolicy that is '250 ExitPolicy=reject :' is a relay, anything else is an exit. Lets continue this by email, you have my address right? (robert at roberthogan.net)

Date: 2008-05-06 20:57
Sender: nobody

Logged In: NO

Hi Praedor,

First off, I don't doubt that you've encountered a bug of some sort here -
either in code or usability. However, I can't replicate this problem at
all. This is what I did:

1. Used the first run wizard to configure Tor as a client and server with
default settings (i.e. exit).
2. Started Tor from Tork.
3. Confirmed that my server was running as an exit. It was. (see below for
the commands to confirm this).
4. Stopped Tor via Tork.
5. Re-ran the wizard and this time selected client and relay server.
6. Started Tor from Tork.
7. Confirmed that my server was not running as an exit.

To help get to the bottom of it you should disable authentication on Tor
and follow the steps you are taking to use TorK to configure Tor as a
relay, and use the following commands to establish how Tor is configured at
each point:

telnet localhost 9051
authenticate
getconf exitpolicy

An exitpolicy that is '250 ExitPolicy=reject *:*' is a relay, anything
else is an exit.

Lets continue this by email, you have my address right? (robert at
roberthogan.net)

TorK - Anonymity Manager for KDE

Tracker: Bugs

Comment ( 1 )

Log in to comment.

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.

About SourceForge

Find Software

Develop Software

Community

Help