September 2019 - tor-commits - lists.torproject.org

[community/develop] Added Fedora Instructions
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 3adaf16263e0a38e70918ad03c9e3ca6ea3929bf Author: Christopher King <bunnyapocalypse(a)protonmail.com> Date: Fri Aug 30 23:55:39 2019 +0000 Added Fedora Instructions So this is what I needed to do in order to get my fedora server up and running as a bridge, and I've added these instructions as if these problems only affect Fedora users, but I would be surprised if that's the case, because the alternative ports that are encouraged in this guide for ORPort and ServerTransportListenAddr are exactly what selinux is supposed to stop. Because of that, I'd imagine that this would function the same on CentOS SUSE and RHEL. As for why the fedora instructions install the executable into normal bin, that's because you run into selinux problems there too when it's in /usr/local/bin , but problems that were more complicated than my tiny selinux knowledge can deal with. policycoreutils-python-utils is needed for semanage. --- .../bridge/centos-rhel-opensuse/contents.lr | 56 ++++++++++++++++++++++ 1 file changed, 56 insertions(+) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index 43f3883..29c68ff 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -21,6 +21,12 @@ yum install git golang tor zypper install tor go git ``` +* Fedora: + +``` +dnf install git golang tor policycoreutils-python-utils +``` + ### 2. Build obfs4proxy and move it into place. 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. @@ -42,8 +48,18 @@ go get gitlab.com/yawning/obfs4.git/obfs4proxy sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ ``` +* Fedora: + +``` +export GOPATH=`mktemp -d` +go get gitlab.com/yawning/obfs4.git/obfs4proxy +sudo cp $GOPATH/bin/obfs4proxy /usr/bin/ +``` + ### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with: +* CentOS / RHEL / OpenSUSE: + ``` RunAsDaemon 1 BridgeRelay 1 @@ -73,6 +89,36 @@ ContactInfo <address(a)email.com> # Pick a nickname that you like for your bridge. This is optional. Nickname PickANickname ``` +* Fedora: + +``` +RunAsDaemon 1 +BridgeRelay 1 + +# Replace "TODO" with a Tor port of your choice. This port must be externally +# reachable. Avoid port 9001 because it's commonly associated with Tor and +# censors may be scanning the Internet for this port. +ORPort TODO + +ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy + +# Replace "TODO" with an obfs4 port of your choice. This port must be +# externally reachable. Avoid port 9001 because it's commonly associated with +# Tor and censors may be scanning the Internet for this port. +ServerTransportListenAddr obfs4 0.0.0.0:TODO + +# Local communication port between Tor and obfs4. Always set this to "auto". +# "Ext" means "extended", not "external". Don't try to set a specific port +# number, nor listen on 0.0.0.0. +ExtORPort auto + +# Replace "<address(a)email.com>" with your email address so we can contact you if +# there are problems with your bridge. This is optional but encouraged. +ContactInfo <address(a)email.com> + +# Pick a nickname that you like for your bridge. This is optional. +Nickname PickANickname +``` Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. @@ -80,8 +126,18 @@ Nickname PickANickname ### 4. Restart tor +* CentOS / RHEL / OpenSUSE: + `systemctl restart tor` +* Fedora: + +``` +sudo semanage port -a -t tor_port_t -p tcp [desired ORPort number set earlier] +sudo semanage port -a -t tor_port_t -p tcp [desired ServerTransportListenAddr port number set earlier] +systemctl restart tor +``` + ### 5. Monitor your logs (usually in your syslog) To confirm your bridge is running with no issues, you should see something like this:

1 0

[community/develop] Fix port number ambiguity and path issue
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit d6cb84fd56b5b05b5b0561aed8eeb789de36e157 Author: Ken Kundert <thenurd(a)nurdletech.com> Date: Fri Aug 30 12:48:27 2019 -0700 Fix port number ambiguity and path issue When I read this I was stumped for a while by the fact that the same name was used for what I believe should be two different values. TODO was used for both the ORPort and the obfs4 port.. I tried to make it clear that these should be two different ports. Also, you install obfs4 into /usr/local/bin but then configured tor to use /usr/bin. Some issues I was unable to resolve: 1. on CentOS Linux release 7.6.1810 I was unable to install obfs4 using 'go get'. go get gitlab.com/yawning/obfs4.git/obfs4proxy # cd .; git clone https://gitlab.com/yawning/utls /tmp/tmp.HMbPtKs8RV/src/gitlab.com/yawning/utls.git error: RPC failed; result=22, HTTP code = 404 fatal: The remote end hung up unexpectedly package gitlab.com/yawning/utls.git: exit status 128 2. On Fedora 30 I was able to install obfs4, but I struggled with selinux. I needed: /sbin/restorecon -v /usr/local/bin/obfs4proxy Relabeled /usr/local/bin/obfs4proxy from system_u:object_r:tor_exec_t:s0 to system_u:object_r:bin_t:s0 and semanage port -a -t tor_port_t -p tcp 4151 to get things working. I suspect your suggested chcon was ill-advised and resulted in the need for me to run restorecon. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index 2d232a7..43f3883 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -48,17 +48,18 @@ sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ RunAsDaemon 1 BridgeRelay 1 -# Replace "TODO" with a Tor port of your choice. This port must be externally +# Replace "TODO1" with a Tor port of your choice. This port must be externally # reachable. Avoid port 9001 because it's commonly associated with Tor and # censors may be scanning the Internet for this port. -ORPort TODO +ORPort TODO1 -ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy +ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy -# Replace "TODO" with an obfs4 port of your choice. This port must be -# externally reachable. Avoid port 9001 because it's commonly associated with +# Replace "TODO2" with an obfs4 port of your choice. This port must be +# externally reachable and must be different from the one specified for ORPort. +# Avoid port 9001 because it's commonly associated with # Tor and censors may be scanning the Internet for this port. -ServerTransportListenAddr obfs4 0.0.0.0:TODO +ServerTransportListenAddr obfs4 0.0.0.0:TODO2 # Local communication port between Tor and obfs4. Always set this to "auto". # "Ext" means "extended", not "external". Don't try to set a specific port

1 0

[community/develop] Move getting help page from bridges to relays - fix #81
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 991d643c903e69d0f49cc644df14bc73c59a4f50 Author: gus <gus(a)torproject.org> Date: Mon Sep 2 06:46:45 2019 -0400 Move getting help page from bridges to relays - fix #81 --- .../{technical-setup/bridge => }/getting-help/contents.lr | 0 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/getting-help/contents.lr b/content/relay-operations/getting-help/contents.lr similarity index 100% rename from content/relay-operations/technical-setup/bridge/getting-help/contents.lr rename to content/relay-operations/getting-help/contents.lr

1 0

[community/develop] Change small typo
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 43aa698da782cf491d06c2d87e1120e655d93964 Author: Christopher King <bunnyapocalypse(a)protonmail.com> Date: Sat Aug 31 16:59:30 2019 +0000 Change small typo I'm still investigating whether or not you run into the same problems that I did on Fedora in other selinux enabled systems (CentOS/RHEL). But I noticed this little thing as well, so I figured I might as well change it --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index 29c68ff..0b28061 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -8,7 +8,7 @@ body: ### 1. Install tor and dependencies -* Redhat / RHEL: +* CentOS / RHEL: ``` yum install epel-release

1 0

[community/develop] Update contents.lr
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit bd410025265a433242689c33c5cc0c7d961d49e6 Author: Christopher King <bunnyapocalypse(a)protonmail.com> Date: Sat Aug 31 19:24:11 2019 +0000 Update contents.lr --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index 0b28061..b297b6d 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -12,7 +12,7 @@ body: ``` yum install epel-release -yum install git golang tor +yum install git golang tor policycoreutils-python-utils ``` * OpenSUSE: @@ -130,7 +130,7 @@ Nickname PickANickname `systemctl restart tor` -* Fedora: +* Fedora / RHEL / CentOS: ``` sudo semanage port -a -t tor_port_t -p tcp [desired ORPort number set earlier]

1 0

[community/develop] Remove full mailing list address and include irc.oftc.net
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 3723f9af891f21a0a2e09e3341939480ec42bf94 Author: gus <gus(a)torproject.org> Date: Mon Sep 2 14:27:25 2019 -0400 Remove full mailing list address and include irc.oftc.net --- templates/relay-operations.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/relay-operations.html b/templates/relay-operations.html index 2ebeb5f..7690b3b 100644 --- a/templates/relay-operations.html +++ b/templates/relay-operations.html @@ -21,7 +21,7 @@ </div> <div class="row py-5 text-center mx-auto"> <h2 class="display-4 text-primary text-center mx-auto my-3">{{ _('Connect with other Relay Operators') }}</h2> - <p class="text-center">{{ _('The best resource of all is the active community of relay operators on tor-relays(a)lists.torproject.org and on IRC in #tor-relays. ') }}</p> + <p class="text-center">{{ _('The best resource of all is the active community of relay operators on tor-relays mailing list and on IRC #tor-relays in irc.oftc.net. ') }}</p> <a class="btn btn-lg btn-outline-primary mx-auto my-3" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays"> {{ _('Relay Operators mailing list') }}<i class="ml-3 pt-2 fas fa-arrow-right"></i> </a>

1 0

[community/develop] Add events
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 31f71c8cb895ca3eb877655387fa171c6fc51c9e Author: hiro <hiro(a)torproject.org> Date: Mon Sep 2 19:18:01 2019 +0200 Add events --- .gitignore | 2 +- templates/outreach.html | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index 41a4e3a..9029559 100644 --- a/.gitignore +++ b/.gitignore @@ -8,7 +8,7 @@ public *.po contents+*.lr -.cache +.cache *.egg-info *.pyc diff --git a/templates/outreach.html b/templates/outreach.html index 18c697a..e35f896 100644 --- a/templates/outreach.html +++ b/templates/outreach.html @@ -34,5 +34,8 @@ </div> <div class="row py-5 text-center mx-auto"> <h2 class="display-4 text-primary text-center mx-auto">{{ _('Upcoming Tor Events') }}</h2> + <div class="col-12"> + {{ render_stream()|safe }} + </div> </div> </div>

1 0

[community/develop] Change getting help url
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 6a082bc83d68471c10d0d7c75ed485c0daa48f84 Author: gus <gus(a)torproject.org> Date: Mon Sep 2 14:28:50 2019 -0400 Change getting help url --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index b297b6d..c0f82d4 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -155,7 +155,7 @@ To confirm your bridge is running with no issues, you should see something like ### 6. Final notes If you are having troubles setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +section](https://community.torproject.org/relay/getting-help/). If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/).

1 0

[community/develop] Change getting help url
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 9a14d2eaa871d62fecc2e7b66f77ff8e7a363347 Author: gus <gus(a)torproject.org> Date: Mon Sep 2 14:29:33 2019 -0400 Change getting help url --- .../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr index 41b4f76..eed3be8 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -82,7 +82,7 @@ To confirm your bridge is running with no issues, you should see something like ### 6. Final notes If you are having troubles setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +section](https://community.torproject.org/relay/getting-help/). If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/).

1 0

[community/develop] Change getting help url
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit b89ab3f176dd419265b9782e1401551773b89757 Author: gus <gus(a)torproject.org> Date: Mon Sep 2 14:30:03 2019 -0400 Change getting help url --- content/relay-operations/technical-setup/bridge/docker/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index f8925a1..ef601f1 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -20,7 +20,7 @@ That's it! Your container should now be bootstrapping your new obfs4 Tor bridge. Make sure to check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). If you are having troubles setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/setup/bridge/getting-help/). +section](https://community.torproject.org/relay/getting-help/). --- html: two-columns-page.html

1 0