Re: [tor-relays] tor-relays Digest, 3 questions on torcc file

2016-09-04 Thread Kenneth Freeman
On 09/03/2016 05:35 PM, jensm1 wrote: > 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". I concur. Generally speaking you really don't have to get under the hood much. Tor's ready to

Re: [tor-relays] tor-relays Digest, 3 questions on torcc file

2016-09-03 Thread jensm1
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

Re: [tor-relays] tor-relays Digest, 3 questions on torcc file

2016-09-03 Thread 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

Re: [tor-relays] tor-relays Digest, 3 questions on torcc file

2016-09-03 Thread Matt Traudt
Daniel Boone The answers to your questions depend on what you want to do. > Log options If you leave them all commented, by default you'll get 'Log notice file /var/log/tor/log'. This is probably what you want unless you're debugging some issue. > ControlPort 9051 I'm **pretty sure** this is

Re: [tor-relays] tor-relays Digest, 3 questions on torcc file

2016-09-03 Thread daniel boone
  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