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

[community/master] quick typo/grammar fix! thanks
by phw＠torproject.org 28 Oct '19

28 Oct '19

commit 6874a557c2f9a7120fff099001ff1af46145f2ac Author: Vinicius Zavam <egypcio(a)googlemail.com> Date: Fri Oct 18 15:16:42 2019 +0000 quick typo/grammar fix! thanks --- .../relay-operations/technical-setup/bridge/dragonflybsd/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr index 630b347..1e4fdf6 100644 --- a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr @@ -41,7 +41,7 @@ For fresh installations, the file `/usr/local/etc/pkg/repos/df-latest.conf.sampl - Avalon (mirror-master.dragonflybsd.org) - Wolfpond (pkg.wolfpond.org) -We can simply edit the **URL** used to point out the repositories on `/usr/local/etc/pkg/repos/df-latest` and that's it! Remember to use **pkg+https://** for Avalon. +We can simply edit the **URL** used to point to the repositories on `/usr/local/etc/pkg/repos/df-latest` and that's it! Remember to use **pkg+https://** for Avalon. After applying all these changes, we update the packages list again and try to check if there's already a new update to apply:

1 0

[community/master] as dfBSD was sad to be added alone, we brought NetBSD to the rescue;
by phw＠torproject.org 28 Oct '19

28 Oct '19

commit 8e1d02a7490dc482ddec1be353ac54b159c8ab5f Author: Vinicius Zavam <egypcio(a)googlemail.com> Date: Fri Oct 4 22:05:44 2019 +0000 as dfBSD was sad to be added alone, we brought NetBSD to the rescue; - of course it runs netbsd ]:-) --- .../technical-setup/bridge/netbsd/contents.lr | 96 ++++++++++++++++++++++ 1 file changed, 96 insertions(+) diff --git a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr new file mode 100644 index 0000000..8262eda --- /dev/null +++ b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr @@ -0,0 +1,96 @@ +_model: page +--- +color: primary +--- +title: NetBSD +--- +html: two-columns-page.html +--- +key: 3 +--- +body: + +### 1. Setup `pkg_add` + +``` +echo "PKG_PATH=http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$(uname -m)/$(uname -r)/All" > /etc/pkg_install.conf +``` + +2. Install `obfs4proxy` and `tor` NetBSD's package + +``` +pkg_add obfs4proxy tor +``` + +### 2. Configure `/usr/pkg/etc/tor/torrc` to run **Tor** as a Bridge + +``` +RunAsDaemon 1 +BridgeRelay 1 + +# 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 TODO1 + +ServerTransportPlugin obfs4 exec /usr/pkg/bin/obfs4proxy + +# 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: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 +# 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 + +Log notice syslog +``` + +Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. + +* Please note that both `ORPort` and the port you used as `TODO2` (for obfs4) must be reachable. If your bridge is behind a firewall or NAT, make sure to open/forward both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. + +* Are you firewalling your NetBSD? If so, make sure that `obfs4proxy` can talk to `tor` over the loopback interface - do not forget to whitelist the **ExtORPort**. + +### 3. Start `tor`: + +``` +ln -sf /usr/pkg/share/examples/rc.d/tor /etc/rc.d/tor +echo "tor=YES" >> /etc/rc.conf +/etc/rc.d/tor start +``` + +### 4. Monitor your logs + +To confirm your bridge is running with no issues, you should see something like this: + +``` +[notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>' +[notice] Your Tor bridge's hashed identity key fingerprint is '<NICKNAME> <HASHED FINGERPRINT>' +[notice] Registered server transport 'obfs4' at '[::]:46396' +[notice] Tor has successfully opened a circuit. Looks like client functionality is working. +[notice] Bootstrapped 100%: Done +[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) +[notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. +``` + +### 5. Final Notes + +If you are having troubles setting up your bridge, have a look at [our help 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/). + +--- +subtitle: How to deploy an obfs4 bridge on NetBSD +--- +section: Bridge +--- +section_id: bridge

1 0

[community/master] consistency for netbsd's bridge setup.
by phw＠torproject.org 28 Oct '19

28 Oct '19

commit 3ebeece7321d2b32510f511b86994a2bde1f64ec Author: Vinicius Zavam <egypcio(a)googlemail.com> Date: Fri Oct 18 15:21:05 2019 +0000 consistency for netbsd's bridge setup. --- content/relay-operations/technical-setup/bridge/netbsd/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr index 41f7b46..33a42a0 100644 --- a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr @@ -58,7 +58,7 @@ Log notice syslog Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. -* Please note that both `ORPort` and the port you used as `TODO2` (for obfs4) must be reachable. If your bridge is behind a firewall or NAT, make sure to open/forward both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. +* Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open/forward both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. * Are you firewalling your NetBSD? If so, make sure that `obfs4proxy` can talk to `tor` over the loopback interface - do not forget to whitelist the **ExtORPort**.

1 0

[community/master] Merge remote-tracking branch 'egypcio/torbsd-bridges'
by phw＠torproject.org 28 Oct '19

28 Oct '19

commit 27a800fa107b40e1c6d76fedd8028a6396863f83 Merge: d15ab1b 8187d99 Author: Philipp Winter <phw(a)nymity.ch> Date: Mon Oct 28 14:06:50 2019 -0700 Merge remote-tracking branch 'egypcio/torbsd-bridges' .../bridge/dragonflybsd/contents.lr | 145 +++++++++++++++++++++ .../technical-setup/bridge/netbsd/contents.lr | 100 ++++++++++++++ 2 files changed, 245 insertions(+)

1 0

[community/master] adding quick note on how to look into netbsd's syslog output (it goes to var/log/messages)
by phw＠torproject.org 28 Oct '19

28 Oct '19

commit 8187d99599370ae48ad33877da43aa8f19fce824 Author: Vinicius Zavam <egypcio(a)googlemail.com> Date: Fri Oct 18 15:24:08 2019 +0000 adding quick note on how to look into netbsd's syslog output (it goes to var/log/messages) --- content/relay-operations/technical-setup/bridge/netbsd/contents.lr | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr index 33a42a0..91eb156 100644 --- a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr @@ -75,6 +75,10 @@ echo "tor=YES" >> /etc/rc.conf To confirm your bridge is running with no issues, you should see something like this: ``` +tail /var/log/messages +``` + +``` [notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>' [notice] Your Tor bridge's hashed identity key fingerprint is '<NICKNAME> <HASHED FINGERPRINT>' [notice] Registered server transport 'obfs4' at '[::]:46396'

1 0

[community/master] providing more consistency on the bridge setups (dragonflybsd here).
by phw＠torproject.org 28 Oct '19

28 Oct '19

commit 440b9e93eb15456dc6f951925be45c5a11459d35 Author: Vinicius Zavam <egypcio(a)googlemail.com> Date: Fri Oct 18 15:19:25 2019 +0000 providing more consistency on the bridge setups (dragonflybsd here). - thanks again for the heads up, @mpguerra and @NullHypothesis --- .../relay-operations/technical-setup/bridge/dragonflybsd/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr index 1e4fdf6..b12ef7e 100644 --- a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr @@ -101,7 +101,7 @@ Log notice file /var/log/tor/notices.log Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. -* Please note that both `ORPort` and the port you used as `TODO2` (for obfs4) must be reachable. If your bridge is behind a firewall or NAT, make sure to open/forward both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. +* Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open/forward both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. * Are you firewalling your DragonflyBSD? If so, make sure that `obfs4proxy` can talk to `tor` over the loopback interface - do not forget to whitelist the **ExtORPort**.

1 0

[tpo/master] Update lego
by hiro＠torproject.org 28 Oct '19

28 Oct '19

commit 1814855746e33f5037e6b578b362c9f1b7a0a125 Author: hiro <hiro(a)torproject.org> Date: Mon Oct 28 21:04:04 2019 +0100 Update lego --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 08f767b..1ade3bb 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 08f767bc33c462c2bc3ae8dd05039c6c3c6d7f39 +Subproject commit 1ade3bbac5071fa061a1290cda4acad8ae3b6f1d

1 0

[lego/master] Change link in banner
by hiro＠torproject.org 28 Oct '19

28 Oct '19

commit 1ade3bbac5071fa061a1290cda4acad8ae3b6f1d Author: hiro <hiro(a)torproject.org> Date: Mon Oct 28 21:03:35 2019 +0100 Change link in banner --- templates/banner.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/banner.html b/templates/banner.html index b1782d7..bafd248 100644 --- a/templates/banner.html +++ b/templates/banner.html @@ -17,7 +17,7 @@ </h2> </div> <div class="row"> - <a class="btn-lg rectangle mb-3 mr-3" href="https://donate.torproject.org">DONATE NOW</a> + <a class="btn-lg rectangle mb-3 mr-3" href="https://torproject.org/donate/donate-tbi-hp1">DONATE NOW</a> <p class="give-today-and-mozi">Give today, and Mozilla will match your donation.</p> </div> </div>

1 0

[styleguide/master] Fix bug
by hiro＠torproject.org 28 Oct '19

28 Oct '19

commit 4e3b5a891ec278ff8e5d2a6dd2aca26a7550b523 Author: hiro <hiro(a)torproject.org> Date: Mon Oct 28 18:41:55 2019 +0100 Fix bug --- templates/layout.html | 4 +--- templates/visuals.html | 2 -- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/templates/layout.html b/templates/layout.html index 8c4f09c..37a97b6 100644 --- a/templates/layout.html +++ b/templates/layout.html @@ -21,8 +21,6 @@ </div> </div> </div> - <footer class="footer"> - {% include 'footer.html' %} - </footer> + {% include 'footer.html' %} </body> </html> diff --git a/templates/visuals.html b/templates/visuals.html index 3c690f6..e637e13 100644 --- a/templates/visuals.html +++ b/templates/visuals.html @@ -505,7 +505,5 @@ </div> </div> -{% include 'footer.html' %} - </main> {% endblock %}

1 0

[styleguide/master] Update for eoy campaign
by hiro＠torproject.org 28 Oct '19

28 Oct '19

commit bc61d4b170059d4af0a6338b804b2912791ae5e0 Author: hiro <hiro(a)torproject.org> Date: Mon Oct 28 18:34:57 2019 +0100 Update for eoy campaign --- lego | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lego b/lego index 3d80025..08f767b 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 3d8002591b1a6df64e27624bd08d7a91d8e4c763 +Subproject commit 08f767bc33c462c2bc3ae8dd05039c6c3c6d7f39

1 0