Miroirs/slackbuilds_ponce
1
0
Fork 0
mirror of https://github.com/Ponce/slackbuilds synced 2024-11-25 10:03:03 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

network/tor: Update torrc sample file.

Browse source 
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
This commit is contained in:
Willy Sudiarto Raharjo 2017-02-11 05:54:33 +07:00
parent cbd770a7a6
commit 8b06bd2813
1 changed files with 88 additions and 52 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

140
network/tor/torrc
View file

@ -1,32 +1,35 @@
## Configuration file for a typical Tor user ## Configuration file for a typical Tor user
## Last updated 16 July 2009 for Tor 0.2.2.1-alpha. ## Last updated 22 September 2015 for Tor 0.2.7.3-alpha.
## (May or may not work for much older or much newer versions of Tor.) ## (may or may not work for much older or much newer versions of Tor.)
## ##
## Lines that begin with "## " try to explain what's going on. Lines ## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them ## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol. ## by removing the "#" symbol.
## ##
## See 'man tor', or https://www.torproject.org/tor-manual.html, ## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file. ## for more options you can use in this file.
## ##
## Tor will look for this file in various places based on your platform: ## Tor will look for this file in various places based on your platform:
## https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc ## https://www.torproject.org/docs/faq#torrc
## ##
## This is a custom Slackware torrc. The original Tor Project torrc file is ## This is a custom Slackware torrc. The original Tor Project torrc file is
## still available as /etc/torrc/torrc.sample ## still available as /etc/tor/torrc.sample
## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
## Replace this with "SocksPort 0" if you plan to run Tor only as a ## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
## relay, and not make any local application connections yourself. ## as a relay, and not make any local application connections yourself.
SocksPort 9050 # what port to open for local application connections #SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.
SocksListenAddress 127.0.0.1 # accept connections only from localhost SOCKSPort 127.0.0.1:9050 # what port to open for local application connections
#SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also #SOCKSPort 192.168.0.1:9100 # Bind to this address:port too.
## Entry policies to allow/deny SOCKS requests based on IP address. ## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept ## First entry that matches wins. If no SOCKSPolicy is set, we accept
## all (and only) requests from SocksListenAddress. ## all (and only) requests that reach a SOCKSPort. Untrusted users who
#SocksPolicy accept 192.168.0.0/16 ## can access your SOCKSPort may be able to learn about the connections
#SocksPolicy reject * ## you make.
#SOCKSPolicy accept 192.168.0.0/16
#SOCKSPolicy accept6 FC00::/7
#SOCKSPolicy reject *
## Logs go to stdout at level "notice" unless redirected by something ## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as ## else, like one of the below lines. You can have as many Log lines as
@ -35,7 +38,6 @@ SocksListenAddress 127.0.0.1 # accept connections only from localhost
## We advise using "notice" in most cases, since anything more verbose ## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs. ## may provide sensitive information to an attacker who obtains the logs.
## ##
## Send all messages of level 'notice' or higher to /var/log/tor/tor.log ## Send all messages of level 'notice' or higher to /var/log/tor/tor.log
Log notice file /var/log/tor/tor.log Log notice file /var/log/tor/tor.log
## Send every possible message to /var/log/tor/debug.log ## Send every possible message to /var/log/tor/debug.log
@ -91,53 +93,67 @@ PidFile /var/run/tor/tor.pid
## Required: what port to advertise for incoming Tor connections. ## Required: what port to advertise for incoming Tor connections.
#ORPort 9001 #ORPort 9001
## If you want to listen on a port other than the one advertised ## If you want to listen on a port other than the one advertised in
## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment the ## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## line below too. You'll need to do ipchains or other port forwarding ## follows. You'll need to do ipchains or other port forwarding
## yourself to make this work. ## yourself to make this work.
#ORListenAddress 0.0.0.0:9090 #ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise
## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com
## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5
## A handle for your relay, so people don't have to refer to it by key. ## A handle for your relay, so people don't have to refer to it by key.
## Nicknames must be between 1 and 19 characters inclusive, and must
## contain only the characters [a-zA-Z0-9].
#Nickname ididnteditheconfig #Nickname ididnteditheconfig
## The IP address or full DNS name for your relay. Leave commented out
## and Tor will guess.
#Address noname.example.com
## Define these to limit how much relayed traffic you will allow. Your ## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must ## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 KB. ## be at least 75 kilobytes per second.
#RelayBandwidthRate 100 KB # Throttle traffic to 100KB/s (800Kbps) ## Note that units for these config options are bytes (per second), not
#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps) ## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
## 2^20, etc.
#RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)
## Use these to restrict the maximum traffic per day, week, or month. ## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies to sent _and_ to received bytes, ## Note that this threshold applies separately to sent and received bytes,
## not to their sum: Setting "4 GB" may allow up to 8 GB ## not to their sum: setting "40 GB" may allow up to 80 GB total before
## total before hibernating. ## hibernating.
## ##
## Set a maximum of 4 gigabytes each way per period. ## Set a maximum of 40 gigabytes each way per period.
#AccountingMax 4 GB #AccountingMax 40 GBytes
## Each period starts daily at midnight (AccountingMax is per day) ## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00 #AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax ## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month) ## is per month)
#AccountingStart month 3 15:00 #AccountingStart month 3 15:00
## Contact info to be published in the directory, so we can contact you ## Administrative contact information for this relay or bridge. This line
## if your relay is misconfigured or something else goes wrong. Google ## can be used to contact you if your relay or bridge is misconfigured or
## indexes this, so spammers might also collect it. ## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Random Person <nobody AT example dot com> #ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one: ## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 1234D/FFFFFFFF Random Person <nobody AT example dot com> #ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
## Uncomment this to mirror directory information for others. Please do ## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth. ## if you have enough bandwidth.
#DirPort 9030 # what port to advertise for directory connections #DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised ## If you want to listen on a port other than the one advertised in
## in DirPort (e.g. to advertise 80 but bind to 9091), uncomment the line ## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## below too. You'll need to do ipchains or other port forwarding yourself ## follows. below too. You'll need to do ipchains or other port
## to make this work. ## forwarding yourself to make this work.
#DirListenAddress 0.0.0.0:9091 #DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## Uncomment to return an arbitrary blob of html on your DirPort. Now you ## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is ## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html in Tor's source ## contacting them. See contrib/tor-exit-notice.html in Tor's source
@ -148,14 +164,22 @@ PidFile /var/run/tor/tor.pid
## key fingerprint of each Tor relay you control, even if they're on ## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid ## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See ## using more than one of your relays in a single circuit. See
## https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleServers ## https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge's fingerprint here, as it would
## break its concealability and potentially reveal its IP/TCP address.
#MyFamily $keyid,$keyid,... #MyFamily $keyid,$keyid,...
## A comma-separated list of exit policies. They're considered first ## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to _replace_ ## to last, and the first match wins.
## the default exit policy, end this with either a reject *:* or an ##
## accept *:*. Otherwise, you're _augmenting_ (prepending to) the ## If you want to allow the same ports on IPv4 and IPv6, write your rules
## default exit policy. Leave commented to just use the default, which is ## using accept/reject *. If you want to allow different ports on IPv4 and
## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules
## using accept/reject *4.
##
## If you want to _replace_ the default exit policy, end this with either a
## reject *:* or an accept *:*. Otherwise, you're _augmenting_ (prepending to)
## the default exit policy. Leave commented to just use the default, which is
## described in the man page or at ## described in the man page or at
## https://www.torproject.org/documentation.html ## https://www.torproject.org/documentation.html
## ##
@ -166,16 +190,28 @@ PidFile /var/run/tor/tor.pid
## you should update your exit policy to reflect this -- otherwise Tor ## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down. ## users will be told that those destinations are down.
## ##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more ## For security, by default Tor rejects connections to private (local)
#ExitPolicy accept *:119 # accept nntp as well as default exit policy ## networks, including to the configured primary public IPv4 and IPv6 addresses,
## and any public IPv4 and IPv6 addresses on any interface on the relay.
## See the man page entry for ExitPolicyRejectPrivate if you want to allow
## "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more
#ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy
#ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy
#ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as default exit policy
#ExitPolicy reject *:* # no exits allowed #ExitPolicy reject *:* # no exits allowed
#
## Bridge relays (or "bridges") are Tor relays that aren't listed in the ## Bridge relays (or "bridges") are Tor relays that aren't listed in the
## main directory. Since there is no complete public list of them, even if an ## main directory. Since there is no complete public list of them, even an
## ISP is filtering connections to all the known Tor relays, they probably ## ISP that filters connections to all the known Tor relays probably
## won't be able to block all the bridges. Also, websites won't treat you ## won't be able to block all the bridges. Also, websites won't treat you
## differently because they won't know you're running Tor. If you can ## differently because they won't know you're running Tor. If you can
## be a real relay, please do; but if not, be a bridge! ## be a real relay, please do; but if not, be a bridge!
#BridgeRelay 1 #BridgeRelay 1
#ExitPolicy reject *:* ## By default, Tor will advertise your bridge to users through various
## mechanisms like https://bridges.torproject.org/. If you want to run
## a private bridge, for example because you'll give out your bridge
## address manually to your friends, uncomment this line:
#PublishServerDescriptor 0