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