Grautier.com - Projekte

Geht nicht gibt es nicht !!!

Benutzer-Werkzeuge

Webseiten-Werkzeuge


faqs:linux:torexitnode

TOR - ExitNode

Beschreibung

Mit dieser Anleitung möchte ich zeigen wie einfach eine TOR-ExitNode aufzubauen ist, TOR ist extra so konzipiert das es so einfach wie möglich ist, Fehler kann man eigentlich nicht viele machen einige kleinere Fallen gibt es trotzdem.

Anleitung

Hinweise

TOR-ExitNoden sind durch das Telemediengesetz §8 geschützt.

§8 Durchleitung von Informationen
(1) Diensteanbieter sind für fremde Informationen, die sie in einem Kommunikationsnetz übermitteln oder zu denen sie den Zugang zur Nutzung vermitteln, nicht verantwortlich, sofern sie
1. die Übermittlung nicht veranlasst,
2. den Adressaten der Übermittelten Informationen nicht ausgewählt und
3. die Übermittelten Informationen nicht ausgewählt oder verändert haben.

Satz 1 findet keine Anwendung, wenn der Dienstanbieter absichtlich mit einem Nutzer seines Dienstes zusammenarbeitet, um rechtswidrige Handlungen zu begehen.

(2) Die Übermittlung von Informationen nach Absatz 1 und die Vermittlung des Zugangs zu ihnen umfasst auch die automatische kurzzeitige Zwischenspeicherung dieser Informationen, soweit dies nur zur Durchführung der Übermittlung im Kommunikationsnetz geschieht und die Informationen nicht länger gespeichert werden, als für die Übermittlung Üblicherweise erforderlich ist.

Vorbereitungen

Als erstes brauchen wir folgende Programme:

tor - Das TOR Programmpaket
tor-arm - Monitoring Programm für die Console

TOR Projekt Quellen installieren (Man sollte diese benutzen da diese immer aktuell sind):

sudo echo  "deb http://deb.torproject.org/torproject.org precise main" >> /etc/apt/sources.list
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 886DDD89  
sudo apt-get update

Programme Installieren:

sudo apt-get install tor tor-arm

Einrichten

Die /etc/tor/torrc mit folgenden Daten füttern:

torrc
## Configuration file for a typical Tor user
## Last updated 22 April 2012 for Tor 0.2.3.14-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 adddress: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
#CookieAuthFileGroupReadable 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 <FQSDomain>
 
## 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 <NICKName>
 
## 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 4000 KB  # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 8000 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 15 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
 
## Contact info to be published in the directory, so we can contact you
## if your relay is misconfigured or something else goes wrong. Google
## indexes this, so spammers might also collect it.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
ContactInfo tor@example.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
 
ExitPolicy accept *:22		# SSH
ExitPolicy accept *:43		# WHOIS
ExitPolicy accept *:53		# ISI-GL
ExitPolicy accept *:79-81	# Finger, HTTP,TOR
ExitPolicy accept *:88		# Kerberos
ExitPolicy accept *:443	# HTTPS
ExitPolicy accept *:465	# SMTP-SSL
ExitPolicy accept *:563	# NNTP-TLS/SSL
ExitPolicy accept *:587	# SMTP
ExitPolicy accept *:706	# Secure Internet Live Conferencing (SILC)
ExitPolicy accept *:873	# ?
ExitPolicy accept *:993	# IMAPS
ExitPolicy accept *:995	# POP3S
ExitPolicy accept *:1194	# OPENVPN
ExitPolicy accept *:1533	# IBM Sametime IM—Virtual Places Chat Microsoft SQL Server
ExitPolicy accept *:2947	# GPSD
ExitPolicy accept *:3386	# GTP' 3GPP GSM/UMTS CDR logging protocol
ExitPolicy accept *:3690	# Subversion
ExitPolicy accept *:4321	# RWhois
ExitPolicy accept *:5031	# ISDNoE
ExitPolicy accept *:5222-5223	# XMPP,XMPP-SSL,
ExitPolicy accept *:8008	# HTTP
ExitPolicy accept *:8080	# HTTP/Proxy
ExitPolicy accept *:8443	# SW Soft Plesk Control Panel, Apache Tomcat SSL, Promise WebPAM SSL
ExitPolicy accept *:9418	# git, Git pack transfer services
ExitPolicy accept *:9420-9422	# MooseFS distributed file system
ExitPolicy accept *:11371	# OpenPGP HTTP Key Server
ExitPolicy reject *:*		# Rejekt Rest
 
## 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
DisableDebuggerAttachment 0

Wichtig !!! als nässtes müsst ihr bei Address eine FQSDomain angeben, und bei Nickname den Namen unter der der TORServer sich melden soll.
Wichtig !!! Auch eine Abuse-Adresse angeben, dieses muss keine Email sein es kann auch ein Link zu einem Formular / Impressum oder Ähnliches sein.

ContactInfo tor@example.com

Bei dem Folgendem stellt ihr ein wie viel ihr eurer Leitung freigeben möchtet, und wie viel pro TAG an Traffic verbraucht werden soll ACHTUNG !!! Die Einstellungen sind für je Down/Upload d.h. bei der Einstellung sind es 20GB am TAG also ~620GB / Monat + Overhead(ca. 500M/Tag)

RelayBandwidthRate 4000 KB
RelayBandwidthBurst 8000 KB
AccountingMax 10 GB
AccountingStart day 00:00

Die Config für die ExitPolicy habe ich mir von den CCC-Servern ausgeliehen und beschriftet, da sind einige Sachen bei die unheimlich viel Traffic verbraten, ihr könnt sie einfach auszukommentieren wenn ihr diese nicht wollt.
Wichtig bei Erweiterungen ist die Liste wird von oben nach unten abgearbeitet d.h. würde das reject *:* oben stehen wehren alle Ports dicht der Server wird dann automatisch zur EntryNode, alles nach dem reject *:* wird Ignoriert.

Wen ihr fertig seit könnt ihr den Service neustarten und euch mit TOR-ARM anschauen ob der Server lauft es dauert allerdings einige Stunden bis sich die Daten im TOR-Netzwerk verbreitet haben, die ersten Verbindungen kommen aber recht schnell zustande.

service tor restart
sudo -u debian-tor arm

sandfrog 24/09/2016 22:33

Diskussion

Geben Sie Ihren Kommentar ein. Wiki-Syntax ist zugelassen:
L Q S N W
 
faqs/linux/torexitnode.txt · Zuletzt geändert: 24/09/2016 22:48 (Externe Bearbeitung)