That’s it! You should see in your logs: Sep 6 12:55:47 Tor: Tor 0.3.3.9 (git-ca1a436fa8e53a32) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2g, Zlib 1.2.8, Liblzma 5.1.0alpha, and Libzstd N/A. Units are being reloaded automatically by edit, so now we just have to restart Tor with: systemctl restart tor Run the following commands and, for both of them, when the editor opens paste what’s in the next box: systemctl edit edit the editor paste the following: We now need to lower the security of Tor systemd process by making an override of Tor’s systemd service files. Let’s now give obfs4proxy the permissions to run on privileged ports: setcap 'cap_net_bind_service=+ep' /usr/bin/obfs4proxyĪnd here we are, at the point of the previous blog post, but on the new Ubuntu16 with the above error. Update the ServerTransportListenAddr with your preferred transport and options. ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxyĪnd configuration is done. We now configure Tor server with the Bridge configuration (update the ContactInfo and Nickname fields with your data): mv /etc/tor/torrc
So now we have latest stable Tor installed on our Ubuntu16 with obfs4proxy as well. Gpg -export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | apt-key add -Īpt -y install tor -keyring obfs4proxy So, in the ancient times I wrote a blog post on how to run a Tor bridge on a non privileged port (> /etc/apt//tor.list
0 kommentar(er)
