Send tor-relays mailing list submissions to
tor-relays@lists.torproject.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
or, via email, send a message with subject or body 'help' to
tor-relays-request@lists.torproject.org
You can reach the person managing the list at
tor-relays-owner@lists.torproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of tor-relays digest..."
Today's Topics:
1. Re: tor-relays Digest, 3 questions on torcc file (Matt Traudt)
2. Re: tor-relays Digest, 3 questions on torcc file (jensm1)
3. Re: tor-relays-strike-snowden (jensm1)
----------------------------------------------------------------------
Message: 1
Date: Sat, 3 Sep 2016 16:18:29 -0400
From: Matt Traudt <sirmatt@ksu.edu>
To: <tor-relays@lists.torproject.org>
Subject: Re: [tor-relays] tor-relays Digest, 3 questions on torcc file
Message-ID: <e8606fce-1429-02de-20a0-7cdfa7bbe45c@ksu.edu>
Content-Type: text/plain; charset="utf-8"
Daniel Boone
I missed your SOCKS question.
If you do not intend to directly use this Tor instance to access the Tor
network, you should leave the SocksPort as it was. By default Tor only
listens on localhost:9050 (as the documentation indicates). Therefore,
even if you *do* intend to use this Tor instance to access the Tor
network, by default you can already point your applications towards
localhost:9050.
So in most cases, this option can be left alone so the default
configuration can do its thing. Either you won't use the SOCKS proxy and
it is harmlessly listening on localhost anyway, or you are like most
people and don't need it to listen on non-localhost non-9050. For either
case, the default behavior is fine.
Hope this helps.
Matt
On 09/03/2016 03:55 PM, daniel boone wrote:
>
> I got a couple of question to ask on the torrc file and I hope one of
> you will direct me.
>
> Ok here we go. I got it working as a relay which i can see in the
> terminal. I just started so it is still testing bandwidth. but this is
> not my questions
>
> 1. on line 18 of mine it is about Socks. I was reading in the man pages
> on this. It was #Socksport 9050. Per the man pages I took out the
> comment and placed as "+" per the page. So now it is *+SOCKSPort 9050 #
> Default: Bind to localhost:9050 for local connections.*
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <
http://lists.torproject.org/pipermail/tor-relays/attachments/20160903/04a566a2/attachment-0001.sig>
------------------------------
Message: 2
Date: Sun, 4 Sep 2016 01:35:50 +0200
From: jensm1 <jensm1@bbjh.de>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] tor-relays Digest, 3 questions on torcc file
Message-ID: <99c2906c-293c-c0cb-0f14-1f92b438b3ce@bbjh.de>
Content-Type: text/plain; charset="utf-8"
I agree to everything Matt said.
A good rule of thumb for tor configuration is "leave everything at
default, unless you've got a reason to change it".
Also keep in mind that configuration files (and especially their
comments) are mostly about what you CAN do, not what you SHOULD do.
Regarding the control port: I think you don't need it at all, unless
you're doing something unusual or don't have ssh access to the computer
tor is running on. If both run on the same machine, arm is doing fine
with just the (unix) control socket.
Regarding the exit settings:
Is this relay running on a computer at your home, Daniel? Is there other
important stuff stored/running on that computer? If the answer to AT
LEAST ONE of those two questions is yes, you should definitely set
"ExitRelay 0" and "ExitPolicy reject *:*".
Actually, you should set this, regardless of the answers, unless you
know exactly, what it means to run an exit-relay and are willing and
prepared to do this.
Jens
Am 03.09.2016 um 22:18 schrieb Matt Traudt:
> Daniel Boone
>
> I missed your SOCKS question.
>
> If you do not intend to directly use this Tor instance to access the Tor
> network, you should leave the SocksPort as it was. By default Tor only
> listens on localhost:9050 (as the documentation indicates). Therefore,
> even if you *do* intend to use this Tor instance to access the Tor
> network, by default you can already point your applications towards
> localhost:9050.
>
> So in most cases, this option can be left alone so the default
> configuration can do its thing. Either you won't use the SOCKS proxy and
> it is harmlessly listening on localhost anyway, or you are like most
> people and don't need it to listen on non-localhost non-9050. For either
> case, the default behavior is fine.
>
> Hope this helps.
>
> Matt
>
> On 09/03/2016 03:55 PM, daniel boone wrote:
>>
>> I got a couple of question to ask on the torrc file and I hope one of
>> you will direct me.
>>
>> Ok here we go. I got it working as a relay which i can see in the
>> terminal. I just started so it is still testing bandwidth. but this is
>> not my questions
>>
>> 1. on line 18 of mine it is about Socks. I was reading in the man pages
>> on this. It was #Socksport 9050. Per the man pages I took out the
>> comment and placed as "+" per the page. So now it is *+SOCKSPort 9050 #
>> Default: Bind to localhost:9050 for local connections.*
>>
>>
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.torproject.org/pipermail/tor-relays/attachments/20160904/6f278d32/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <
http://lists.torproject.org/pipermail/tor-relays/attachments/20160904/6f278d32/attachment-0001.sig>
------------------------------
Message: 3
Date: Sun, 4 Sep 2016 01:38:28 +0200
From: jensm1 <jensm1@bbjh.de>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] tor-relays-strike-snowden
Message-ID: <0a8ee6b6-fff3-9e0a-9af8-29e613133642@bbjh.de>
Content-Type: text/plain; charset="utf-8"
First, let me welcome you to the world of relay operators! It's always
nice to see new faces here, because it means I'm not the only "new guy"
(just started running a relay not that long ago). Of course you won't be
kicked out just for that one mail! I've seen a lot of worse FUD on here,
which is probably why I reacted like I did, your mail just happened to
be the last straw.
If you still have problems with your relay, you could try to ask your
(specific!) questions here or on the tor stackexchange. I'll also be
happy to help you, if I can.
Jens
Am 03.09.2016 um 16:59 schrieb daniel boone:
>
> Jesm1, sorry about my rant. I am new to working with a relay and also
> to Tor. Please bear with me on all of this. Give me a Chance. I just
> wanted to help the project and not sit on my ass like some are afraid
> to do. I will admitt i need to learn a few things on here. My mouth
> for the first one. As for Snowden, he worked for a SubContractor and
> was brought into the CIA or the NSA that way. I think it is wonderful
> what the man did. He brought it all out in the OPEN for the world to
> see. To see just how corrupt the security agency's are over in the
> States. Look how they treated him. A man that told the whole truth and
> if he would go back they would Kill Him.
> I've said enough on that Jesm. I need some work and that is why I came
> to the mailing list and Hope I can get some of my understanding of the
> whole project and only Hope I am not cut from here cause of this. I
> did get my relay running and it was what I was doing wrong on the
> torcc file. Please Lets shake hands and start over. That is all i can
> ask. Hope you take me up on it. The #tor chat room was of no help for
> they just dont seem to want to help some with new questions.
> -db-
>
[snip lengthy quote of digest]
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.torproject.org/pipermail/tor-relays/attachments/20160904/af206206/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
------------------------------
End of tor-relays Digest, Vol 68, Issue 12
******************************************