I'm new into TOR Network and I got a problem.
I saw on this page (https://bitcointalk.org/index.php?topic=331077.80) that this torcc config file is better than the default one for your anonymity
Here's my torcc config file:
## Configuration file for a typical Tor user
## Last updated 9 October 2013 for Tor 0.2.5.2-alpha.
## (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
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc
## Tor opens a socks proxy on port 9050 by default -- even if you don't
## configure one below. Set "SocksPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SocksPort 9050 # Default: Bind to localhost:9050 for local connections.
#SocksPort 192.168.0.1:9100 # Bind to this address:port too.
## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests that reach a SocksPort. Untrusted users who
## can access your SocksPort may be able to learn about the connections
## you make.
#SocksPolicy accept 192.168.0.0/16
#SocksPolicy reject *
## 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
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr
## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
RunAsDaemon 1
## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
DataDirectory /var/lib/tor
## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1
############### This section is just for location-hidden services ###
## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.
#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22
################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.
## Required: what port to advertise for incoming Tor connections.
#ORPort 9001
## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#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.
#Nickname ididnteditheconfig
## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 KB.
## Note that units for these config options are bytes per second, not bits
## per second, and that prefixes are binary prefixes, i.e. 2^10, 2^20, etc.
#RelayBandwidthRate 100 KB # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)
## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received bytes,
## not to their sum: setting "4 GB" may allow up to 8 GB total before
## hibernating.
##
## Set a maximum of 4 gigabytes each way per period.
#AccountingMax 4 GB
## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month)
#AccountingStart month 3 15:00
## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## 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>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised in
## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## follows. below too. You'll need to do ipchains or other port
## forwarding yourself to make this work.
#DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## 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
## contacting them. See contrib/tor-exit-notice.html in Tor's source
## distribution for a sample.
#DirPortFrontPage /etc/tor/tor-exit-notice.html
## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
## https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge's fingerprint here, as it would
## break its concealability and potentionally reveal its IP/TCP address.
#MyFamily $keyid,$keyid,...
## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. 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
## https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
## For security, by default Tor rejects connections to private (local)
## networks, including to your public IP address. See the man page entry
## for ExitPolicyRejectPrivate if you want to allow "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
ExitPolicy reject *:* # no exits allowed
## 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 an
## 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
## 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!
#BridgeRelay 1
## 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
User tor
VirtualAddrNetwork 10.192.0.0/16
TransPort 9040
TransListenAddress 172.16.1.1
DNSPort 9053
DNSListenAddress 172.16.1.1
AutomapHostsOnResolve 1
AutomapHostsSuffixes .exit,.onion
ControlPort 9051
AvoidDiskWrites 1
ClientTransportPlugin obfs2,obfs3,scramblesuit exec /usr/bin/obfsclient
ClientOnly 1
EnforceDistinctSubnets 0
UseEntryGuards 1
NumEntryGuards 8
GeoIPExcludeUnknown 1
StrictNodes 1
EntryNodes AutonomyCube,AccessNow000,AccessNow001,AccessNow002,AccessNow003,AccessNow004,AccessNow005,AccessNow006,AccessNow007,AccessNow008,AccessNow009,AccessNow010,AccessNow011,AccessNow012,AccessNow013,AccessNow014,AccessNow015,AccessNow016,AccessNow017,AccessNow018,AccessNow019,DigiGesTor1e1,DigiGesTor1e2,DigiGesTor1e3,DigiGesTor1e4,DigiGesTor2e1,DigiGesTor2e2,DigiGesTor2e3,DigiGesTor2e4,orion,orilla,destiny,chulak,aurora,assk,alf,sofia,politkovskaja,lumumba,HaveHeart,hessel0,hessel1,hessel2,edwardsnowden0,edwardsnowden1,edwardsnowden2,ekumen,marcuse1,marcuse2,marylou1,marylou2,chaoscomputerclub27,chaoscomputerclub28,chaoscomputerclub29,chaoscomputerclub30,chaoscomputerclub31,chaoscomputerclub32,chaoscomputerclub33,chaoscomputerclub34,atticus,blanqui,thoreau,enjolras,luxemburg,bakunin,bakunin2,bakunin3,bakunin4,jaures,jaures2,jaures3,jaures4,DFRI0,DFRI1,DFRI3,DFRI4,DFRI5,DFRI6,DFRI7,hviv100,hviv104,hviv105,wagtail,toreffiorg,startor0fr,startor0de,startor0nl,startor0lv,startor0se,apx1,apx2,apx3,torrelay1ph3xat,torrelay2ph3xat,symphony,vikingolaf,vikinguthar,vikinghelga,vikingbjorn,tor1multisec,tor2multisec,tor3multisec,tor4multisec,tor5multisec,CalyxInstitute07,SIGAINT1,SIGAINT2,SIGAINT3,SIGAINT4,saveyourprivacyex1,saveyourprivacyexit
ExcludeNodes Unnamed,default,kasperskytor04,37.221.171.234,tylerlockedotorg,198.58.115.210,kebab,193.142.30.66,RedOctober1917,dannenberg,193.23.244.244,dizum,194.109.206.212,Faravahar,154.35.175.225,gabelmoo,131.188.40.189,longclaw,199.254.238.52,maatuska,171.25.193.9,moria1,128.31.0.34,tor26,86.59.21.38,Tonga,82.94.251.203,{AR},{AU},{AT},{BR},{BG},{KH},{CA},{CL},{CR},{EG},{GE},{GG},{IS},{IN},{ID},{IL},{MA},{NA},{NG},{PK},{PT},{QA},{SA},{SG},{ZA},{ES},{TW},{TH},{GB},{US},{VE},{VN}
ExcludeExitNodes {AR},{AU},{AT},{BR},{BG},{KH},{CA},{CL},{CR},{EG},{GE},{GG},{IS},{IN},{ID},{IL},{MA},{NA},{NG},{PK},{PT},{QA},{SA},{SG},{ZA},{ES},{TW},{TH},{GB},{US},{VE},{VN}
ExitNodes AutonomyCube,85.16.128.242,85.16.128.243,85.16.128.244,85.16.128.245,AccessNow000,AccessNow001,176.10.99.200,AccessNow002,AccessNow003,176.10.99.201,AccessNow004,AccessNow005,176.10.99.202,AccessNow006,AccessNow007,176.10.99.203,AccessNow008,AccessNow009,176.10.99.204,AccessNow010,AccessNow011,176.10.99.205,AccessNow012,AccessNow013,176.10.99.206,AccessNow014,AccessNow015,176.10.99.207,AccessNow016,AccessNow017,176.10.99.208,AccessNow018,AccessNow019,176.10.99.209,DigiGesTor1e1,DigiGesTor1e2,176.10.104.240,DigiGesTor1e3,DigiGesTor1e4,176.10.104.241,DigiGesTor2e1,DigiGesTor2e2,176.10.104.243,DigiGesTor2e3,DigiGesTor2e4,176.10.104.244,orion,94.242.246.24,orilla,94.242.252.41,destiny,94.242.246.23,chulak,176.126.252.11,aurora,176.126.252.12,assk,62.102.148.67,alf,77.247.181.166,sofia,77.247.181.162,politkovskaja,77.247.181.165,lumumba,77.247.181.163,HaveHeart,77.247.181.164,hessel0,109.163.234.2,hessel1,109.163.234.4,hessel2,109.163.234.5,edwardsnowden0,109.163.234.7,edwardsnowden1,109.163.234.8,edwardsnowden2,109.163.234.9,ekumen,95.142.161.63,marcuse1,178.20.55.16,marcuse2,178.20.55.18,marylou1,marylou2,89.234.157.254,chaoscomputerclub27,77.244.254.227,chaoscomputerclub28,77.244.254.228,chaoscomputerclub29,77.244.254.229,chaoscomputerclub30,77.244.254.230,chaoscomputerclub31,217.115.10.131,chaoscomputerclub32,217.115.10.132,chaoscomputerclub33,217.115.10.133,chaoscomputerclub34,217.115.10.134,atticus,46.239.117.180,blanqui,thoreau,46.165.221.166,enjolras,81.89.96.88,luxemburg,81.89.96.89,bakunin,178.16.208.57,bakunin2,178.16.208.59,bakunin3,178.16.208.61,bakunin4,178.16.208.55,jaures,178.16.208.56,jaures2,178.16.208.58,jaures3,178.16.208.60,jaures4,178.16.208.62,DFRI0,171.25.193.20,DFRI1,171.25.193.77,DFRI3,171.25.193.235,DFRI4,171.25.193.78,DFRI5,171.25.193.25,DFRI6,171.25.193.132,DFRI7,171.25.193.131,hviv100,194.104.0.100,hviv104,192.42.116.16,hviv105,79.98.107.90,wagtail,77.109.139.87,startor0se,95.215.45.187,startor0lv,185.61.149.43,apx1,176.9.25.72,apx2,85.10.210.199,apx3,5.9.36.66,toreffiorg,212.16.104.33,saveyourprivacyex1,185.100.86.100,saveyourprivacyexit,185.100.84.82,vikingolaf,193.107.85.61,vikinguthar,193.107.85.62,vikinghelga,193.107.85.56,vikingbjorn,193.107.85.57,tor1multisec,193.90.12.86,tor2multisec,193.90.12.87,tor3multisec,193.90.12.88,tor4multisec,193.90.12.89,tor5multisec,193.90.12.90,CalyxInstitute07,82.94.251.227
LongLivedPorts 21, 22, 80, 443, 706, 1863, 5050, 5190, 5222, 5223, 6523, 6667, 6697, 8300, 9001, 9030
So basically I'm trying to use UseBridges 1 option but is not connecting to the TOR Network.
I've tried to put StricNodes to 0 and I got the same problem.
I feel safer to use Bridges but since I can't use them with this torcc config file, I'm asking you guys for help.
What's wrong with my torcc config file? Why I can't use bridges?
Thank you very much!
