Browse Source
* replace torrc file by command lines arguments set in restart script. restructure docker-tor.conf for homogeneity. define env vars in Dockerfile for easier tuning (for pi4 and others platforms) * bump version of tor image * update doc * merge tor bridges config optionsumbrel
kenshin samourai
5 years ago
committed by
nickodev
nickodev
11 changed files with 156 additions and 141 deletions
@ -1,16 +1,34 @@ |
|||
|
|||
######################################### |
|||
# CONFIGURATION OF TOR CONTAINER |
|||
######################################### |
|||
|
|||
# |
|||
# USE TOR BRIDGES |
|||
# |
|||
# To get Tor bridges head over to https://bridges.torproject.org and click on |
|||
# Get bridges, then you will see a form with "Advanced Options" header |
|||
# leave the Pluggable Transport as obfs4 and click on Get Bridges button |
|||
# solve the captcah, you will get the bridge addresses (usually 3) |
|||
# Add these bridges with the help of the below template |
|||
# you need to prefix those with the word "Bridge" and have each of them in a new line. |
|||
# At last, set UseBridges to 1 so the Tor container uses the bridges you add in previous steps. |
|||
# |
|||
# Then, set TOR_USE_BRIDGES to "on" and initialize the TOR_BRIDGE_n options |
|||
# with the 3 lines generated by the online tool. |
|||
# |
|||
# For instance, if the first line generated by the tool is: |
|||
# obfs4 24.106.248.94:65531 B9EFBC5... cert=yrX... iat-mode=0 |
|||
# You will have to set: |
|||
# TOR_BRIDGE_1=obfs4 24.106.248.94:65531 B9EFBC5... cert=yrX... iat-mode=0 |
|||
# |
|||
|
|||
|
|||
# Activate the use of Tor bridges |
|||
# Value: on | off |
|||
TOR_USE_BRIDGES=off |
|||
|
|||
# Bridge 1 |
|||
TOR_BRIDGE_1=ToBeDefined |
|||
|
|||
UseBridges 0 |
|||
#Bridge obfs4 IP:PORT 1111222233334444 cert=XXXXYYYYZZZZ iat-mode=0 |
|||
# Bridge 2 |
|||
TOR_BRIDGE_2=ToBeDefined |
|||
|
|||
# Bridge 3 |
|||
TOR_BRIDGE_3=ToBeDefined |
|||
|
|||
@ -1,44 +0,0 @@ |
|||
## 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. |
|||
|
|||
# Socks is only available from dojonet |
|||
SocksPort 172.28.1.4:9050 |
|||
|
|||
## 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. |
|||
|
|||
# Socks is only available from dojonet |
|||
SocksPolicy accept 172.28.0.0/16 |
|||
SocksPolicy reject * |
|||
|
|||
## 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/.tor |
|||
DataDirectoryGroupReadable 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/hsv2dojo |
|||
HiddenServiceVersion 2 |
|||
HiddenServicePort 80 172.29.1.3:80 |
|||
|
|||
HiddenServiceDir /var/lib/tor/hsv3dojo |
|||
HiddenServiceVersion 3 |
|||
HiddenServicePort 80 172.29.1.3:80 |
|||
|
|||
HiddenServiceDir /var/lib/tor/hsv2bitcoind |
|||
HiddenServiceVersion 2 |
|||
HiddenServicePort 8333 172.28.1.5:8333 |
|||
HiddenServiceDirGroupReadable 1 |
|||
@ -1,48 +0,0 @@ |
|||
## 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. |
|||
|
|||
# Socks is only available from dojonet |
|||
SocksPort 172.28.1.4:9050 |
|||
|
|||
## 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. |
|||
|
|||
# Socks is only available from dojonet |
|||
SocksPolicy accept 172.28.0.0/16 |
|||
SocksPolicy reject * |
|||
|
|||
## 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/.tor |
|||
DataDirectoryGroupReadable 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/hsv2dojo |
|||
HiddenServiceVersion 2 |
|||
HiddenServicePort 80 172.29.1.3:80 |
|||
|
|||
HiddenServiceDir /var/lib/tor/hsv3dojo |
|||
HiddenServiceVersion 3 |
|||
HiddenServicePort 80 172.29.1.3:80 |
|||
|
|||
HiddenServiceDir /var/lib/tor/hsv2bitcoind |
|||
HiddenServiceVersion 2 |
|||
HiddenServicePort 8333 172.28.1.5:8333 |
|||
HiddenServiceDirGroupReadable 1 |
|||
|
|||
# Tor Bridges configuration |
|||
ClientTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy |
|||
|
|||
Loading…
Reference in new issue