If your bridge is now running, check out the post-install notes.Much of the episode was spent showing Richard spending time with Lily. If you are having trouble setting up your bridge, have a look at our help section. Self-testing indicates your ORPort is reachable from the outside. (this may take up to 20 minutes - look for log messages indicating success) Now checking whether ORPort :3818 is reachable. Looks like client functionality is working. Registered server transport 'obfs4' at ':46396' Your Tor bridge's hashed identity key fingerprint is ' ' To confirm your bridge is running with no issues, you should see something like this (usually in /var/log/tor/log or /var/log/syslog): Your Tor server's identity key fingerprint is ' ' Should you use an older release like CentOS/RHEL 6, that will be: # service tor enable or restart it if it was running already, so configurations take effect Recent versions os CentOS/RHEL which ship with systemd: # systemctl enable -now tor Sudo semanage port -a -t tor_port_t -p tcp You can use our reachability test to see if your obfs4 port is reachable from the Internet. If your bridge is behind a firewall or NAT, make sure to open both ports. Note that both Tor's OR port and its obfs4 port must be reachable.This is optional.ĭon't forget to change the ORPort, ServerTransportListenAddr, ContactInfo, and Nickname options. # Pick a nickname that you like for your bridge. # Replace "" with your email address so we can contact you if # "Ext" means "extended", not "external". # Local communication port between Tor and obfs4. ServerTransportListenAddr obfs4 0.0.0.0:TODO2 # Tor and censors may be scanning the Internet for this port. # Avoid port 9001 because it's commonly associated with # externally reachable and must be different from the one specified for ORPort. # Replace "TODO2" with an obfs4 port of your choice. ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy # censors may be scanning the Internet for this port. Avoid port 9001 because it's commonly associated with Tor and # Replace "TODO1" with a Tor port of your choice. Edit your Tor config file, usually located at /etc/tor/torrc and replace its content with: RunAsDaemon 1 # chcon -reference=/usr/bin/tor /usr/local/bin/obfs4proxyĦ. Sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ Now build the binary, and move it to a proper directory: export GOPATH='mktemp -d'
#Tor project hopes replace code install#
Install the golang package and other dependencies: # yum install git golang policycoreutils-python-utils Heavily outdated versions of git can make go get fail, so try upgrading to a more recent git version if you're running into this problem. This will also happens when installing packages from Tor's repository for the first time - again you must ensure the key matches. Please ensure the key matches with the one available on the Fedora Project website. Please note that when you are installing the first package from the EPEL repository you will be asked about verifying the EPEL's GPG signing key. Once you are set with EPEL and the Tor repositories, you are now able to install the package: # yum install tor Name=Tor for Enterprise Linux $releasever - $basearch Configure Tor Project's RepositoryĬonfiguring the Tor Project's Repository for CentOS/RHEL consists basically on setting up /etc//Tor.repo with the following content: If you are on a recent version that uses dnf, please keep using it for the following steps where yum is called on this setup guide. Recent versions of CentOS/RHEL are using dnf instead of yum: # dnf install epel-release To do so, you must install the epel-release package: # yum install epel-release To install the tor package on CentOS/RHEL, you need to enable the use of the EPEL Repository first.
#Tor project hopes replace code software#
One of the most important things to keep your relay secure is to install security updates timely and ideally automatically so you can not forget about it.įollow the instructions to enable automatic software updates for your operating system.