tor-commits March 2021

tor-commits@lists.torproject.org

17 participants
2169 discussions

[gettor-web/master] Merge commit '41119de320b258d8a83ad42e3f3a48b15cf74622'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 37da576b10f1fa72c9ecdda758f7b650e2d40354 Merge: 3527d5b 41119de Author: hiro <hiro(a)torproject.org> Date: Wed Mar 24 18:05:37 2021 +0100 Merge commit '41119de320b258d8a83ad42e3f3a48b15cf74622' GetTor.lektorproject | 25 ------------------------- configs/i18n.ini | 2 +- databags/alternatives.ini | 36 ------------------------------------ models/page.ini | 2 ++ 4 files changed, 3 insertions(+), 62 deletions(-)

1 0

[gettor-web/master] add first .htaccess file as part of https://gitlab.torproject.org/tpo/anti-censorship/gettor-project/gettor-web/-/issues/2
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 39756ac80e44b433322ae35a137e9ca3e1725607 Author: emma peel <emma.peel(a)riseup.net> Date: Wed Mar 24 12:19:52 2021 +0100 add first .htaccess file as part of https://gitlab.torproject.org/tpo/anti-censorship/gettor-project/gettor-web… --- .htaccess | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/.htaccess b/.htaccess new file mode 100644 index 0000000..5d11524 --- /dev/null +++ b/.htaccess @@ -0,0 +1,21 @@ +RewriteEngine On + +# forward requests in /en and /en-US to the root folder +RewriteRule ^(en|en-US)$ / [R=302,L] +RewriteRule ^(en|en-US)/(.*) /$2 [R=302,L] + +# Rewrites for languages that have a different mapping in the page than in TBB +RewriteRule ^(es-ES|es-MX|es-CO|es-AR)(.*) /es$2 [R=302,L] + +# we have only one translation for this locales +RewriteRule ^(bn-BD|bn-IN)(.*) /bn$2 [R=302,L] + +# we call this locale different than mozilla +RewriteRule ^ga-IE/(.*) /ga$1 [R=302,L] + +# Rewrites for languages that have a Tor Browser release +# but don't have a gettor website translation +# You can see them at https://dist.torproject.org/torbrowser/, pick the last alpha for the most languages +# this languages are the translation priority for the gettor website +RewriteRule ^(ar|ca|cs|da|de|el|fa|ga|he|hu|id|is|it|ja|ka|ko|lt|mk|ms|nb-NO|nl|pl|pt-PT|ro|ru|sv-SE|th|tr|vi|zh-CN|zh-TW)$ / [R=302,L] +RewriteRule ^(ar|ca|cs|da|de|el|fa|ga|he|hu|id|is|it|ja|ka|ko|lt|mk|ms|nb-NO|nl|pl|pt-PT|ro|ru|sv-SE|th|tr|vi|zh-CN|zh-TW)/(.*) /$2 [R=302,L]

1 0

[gettor-web/master] Merge commit '39756ac80e44b433322ae35a137e9ca3e1725607'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 3527d5b5f85bb517e530ba36898f30db1dc692c3 Merge: 400176e 39756ac Author: hiro <hiro(a)torproject.org> Date: Wed Mar 24 18:04:39 2021 +0100 Merge commit '39756ac80e44b433322ae35a137e9ca3e1725607' .htaccess | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+)

1 0

[Git][tpo/applications/android-components] Pushed new branch android-components-73.0.11-10.5-1
by Matthew Finkel 24 Mar '21

24 Mar '21

Matthew Finkel pushed new branch android-components-73.0.11-10.5-1 at The Tor Project / Applications / android-components -- View it on GitLab: https://gitlab.torproject.org/tpo/applications/android-components/-/tree/an… You're receiving this email because of your account on gitlab.torproject.org.

1 0

[Git][tpo/applications/fenix] Pushed new branch tor-browser-87.0.0-10.5-1
by Matthew Finkel 24 Mar '21

24 Mar '21

Matthew Finkel pushed new branch tor-browser-87.0.0-10.5-1 at The Tor Project / Applications / fenix -- View it on GitLab: https://gitlab.torproject.org/tpo/applications/fenix/-/tree/tor-browser-87.… You're receiving this email because of your account on gitlab.torproject.org.

1 0

[community/staging] Edit content. Find out why not all slides are built
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 6ad90753504cd7305e586962d952f242f413672f Author: hiro <hiro(a)torproject.org> Date: Wed Mar 24 17:38:23 2021 +0100 Edit content. Find out why not all slides are built --- content/training/resources/tor-training/contents.lr | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index f09ea6c..fa5c835 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -64,7 +64,8 @@ background_image: '/static/images/onion-white.png' ---- description: - ---- +---- + #### slide #### title: Guard/middle (aka non-exit) relay

1 0

[community/staging] Add localization fields in model and flowblock
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 5ae6511eae1872ce598143b0f676bab081130bb2 Author: hiro <hiro(a)torproject.org> Date: Wed Mar 24 13:49:04 2021 +0100 Add localization fields in model and flowblock --- flowblocks/slide.ini | 3 +++ models/slideshow.ini | 5 ++++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/flowblocks/slide.ini b/flowblocks/slide.ini index 23cf3fb..06d1075 100644 --- a/flowblocks/slide.ini +++ b/flowblocks/slide.ini @@ -15,14 +15,17 @@ translate = True label = Image type = select source = record.attachments.images +translate = False [fields.background] label = Background color type = string +translate = False [fields.layout] label = Slide layout type = string +translate = False [fields.background-image] label = Background image diff --git a/models/slideshow.ini b/models/slideshow.ini index 7d0116a..3f2062f 100644 --- a/models/slideshow.ini +++ b/models/slideshow.ini @@ -15,6 +15,7 @@ translate = True [fields.author] label = Author type = string +translate = False [fields.subtitle] label = Subtitle @@ -25,16 +26,18 @@ translate = True label = Slides type = flow flow_blocks = slide -translate = False [fields.color] label = Color type = string +translate = False [fields.image] label = image type = string +translate = False [fields.background] label = background type = string +translate = False

1 0

[community/staging] Use string for localization
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 2ba3cee47c2d184e061668ab4caa4d3237f5f1f9 Author: hiro <hiro(a)torproject.org> Date: Sun Mar 21 20:06:09 2021 +0100 Use string for localization --- content/outreach/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/outreach/contents.lr b/content/outreach/contents.lr index cd2b5fe..9cf4a65 100644 --- a/content/outreach/contents.lr +++ b/content/outreach/contents.lr @@ -1,4 +1,4 @@ -section: Community +section: community --- section_id: outreach ---

1 0

[community/staging] Removing content from the slideshow to see if it has any issue with building
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit fb62fd3c408ad04c0f517fad51273020c387c79a Author: hiro <hiro(a)torproject.org> Date: Wed Mar 24 14:12:12 2021 +0100 Removing content from the slideshow to see if it has any issue with building --- .../training/resources/tor-training/contents.lr | 462 --------------------- 1 file changed, 462 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 4a38efa..7e56f12 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -53,465 +53,3 @@ By running a Tor relay you can help make the Tor network: - more robust against attacks - more stable in case of outages - safer for its users (spying on more relays is harder than on a few) - - -#### slide #### -title: Types of Relays ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Guard/middle (aka non-exit) relay ----- -description: -- A guard is the first relay in the chain of 3 relays building a Tor circuit. -- A middle relay is neither a guard nor an exit, but acts as the second hop between the two. -- To become a guard, a relay has to be stable and fast (at least 2MByte/s) otherwise it will remain a middle relay. - - -#### slide #### -title: Exit relay ----- -description: -- The exit relay is the final relay in a Tor circuit, the one that sends traffic out its destination. -- That's why exit relays have the greatest legal exposure and liability of all the relays. -- Before running an exit relay, check it with your local digital rights organization. -- **You should not run a Tor exit relay from your home** - - -#### slide #### -title: Bridge ----- -description: -- A bridge is a node in the network that isn't listed in the public Tor directory, which make it harder for ISPs and governments to block it. -- Bridges are relatively easy, low-risk and low bandwidth Tor nodes to operate. -- And there's another special kind of bridge: Pluggable transports. It hides your tor traffic by adding an additional layer of obfuscation. - - -#### slide #### -title: The lifecycle of a new relay ----- -description: -Non-exit relays pass by a lifecycle of four phases (defined by days): -- Days 0-3: the unmeasured phase -- Days 3-8: network authorities start the remote measurement phase (the ramp-up guard phase) -- Days 8-68: guard phase (where load counter intuitively drops and then rises higher) - - -#### slide #### -title: The lifecycle of a new relay ----- -description: -- And after 68 days, if the relay is stable and fast enough, it receives a Guard flag (steady-state guard phase). -- Exit relays also have a lifecycle more or less similar. -- Read about all the phases in: [https://blog.torproject.org/lifecycle-new-relay](https://blog.torproject.or… - - -#### slide #### -title: Relay requirements ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Before we start ----- -description: -- Never run a relay without the consent of network administrator or machine owner. Read the Terms of Service (ToS) first, so you don’t lose money. -- Choose which type of relay you will host. Non-exit relay is a easy way to start helping the network. -- Read the documentation: [https://torproject.org/tor-relays](https://torproject.org/tor-relays) - - -#### slide #### -title: Bandwidth requirements ----- -description: -- At least 16 Mbit/s (Mbps) upload and download bandwidth available for Tor. More is better. -- The minimum requirements for a relay are 10 Mbit/s (Mbps). -- If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a bridge with obfs4 support. - - -#### slide #### -title: Monthly outbound traffic ----- -description: -- It is required to use a minimum of 100 GByte of outbound/incoming traffic per month. -- If you have a metered plan you might want to configure tor to only use a given amount of bandwidth or monthly traffic. -- More (>2 TB/month) is better and recommended - - -#### slide #### -title: Public IPv4 address ----- -description: -- Every relay needs a public IPv4 address - either directly on the host (preferred) or via NAT and port forwarding. -- The IPv4 address is not required to be static but static IP addresses are preferred. -- Your IPv4 address should remain unchanged for at least 3 hours (network consensus). -- You can only run two Tor relays per public IPv4. - - -#### slide #### -title: Other requirements ----- -description: -- Memory: A <40 Mbit/s non-exit relay should have at least 512 MB of RAM available. -- Disk storage: Tor does not need much disk storage. A typical Tor relay needs less than 200 MB. - -#### slide #### -title: Other requirements ----- -description: -- Any modern CPU should be fine. -- Uptime: Ideally the relay runs on a server which runs 24/7. - - -#### slide #### -title: Choosing your relay hosting ----- -description: -- Tor community maintain the list GoodBadISPs, about the experience of running relays: https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs -- Some providers only allow non-exit relays, so before buying a service, check the GoodBadISPs. - - -#### slide #### -title: Choosing your relay hosting ----- -description: -- This can cost anywhere between $3.00/mo and thousands per month. - - -#### slide #### -title: Technical setup ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Non-exit relay - Debian/Ubuntu ----- -description: -- Enable the Torproject package repository -- Install the tor package - -``` - $ apt update && apt install tor -``` - - -#### slide #### -title: Non-exit relay - Debian/Ubuntu ----- -description: -- Put the configuration file `/etc/tor/torrc` in place: -``` - Nickname myNiceRelay - ExitRelay 0 - SocksPort 0 - ControORPort 443 - lSocket 0 - ContactInfo tor-operator@your-emailaddress-domain - Log notice syslog -``` - - -#### slide #### -title: Non-exit relay - Debian/Ubuntu ----- -description: -- Restart the tor daemon: - -``` - $ systemctl restart tor@default -``` - - -#### slide #### -title: Non-exit relay - FreeBSD ----- -description: -- Install the tor package - -``` - pkg install tor ca_root_nss -``` - - -#### slide #### -title: Non-exit relay - FreeBSD ----- -description: - - Edit the configuration `file/usr/local/etc/tor/torrc` - -``` - Nickname myNiceRelay - ORPort 9001 - ExitRelay 0 - SocksPort 0 - ControlSocket 0 - ContactInfo tor-operator@your-emailaddress-domain - Log notice syslog -``` - - -#### slide #### -title: Non-exit relay - FreeBSD ----- -description: -- Ensure that the random_id sysctl setting is enabled: - -``` - echo "net.inet.ip.random_id=1" >> /etc/sysctl.conf - sysctl net.inet.ip.random_id=1 -``` - - -#### slide #### -title: Non-exit relay - FreeBSD ----- -description: -- Start the tor daemon and make sure it starts at boot: - -``` - sysrc tor_enable=YES - service tor start -``` - - -#### slide #### -title: Non-exit relay - FreeBSD ----- -description: -Optional, but recommended to get package updates faster: -[https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD](https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD) - - -#### slide #### -title: Verify that your relay works ----- -description: - -After restarting the service, verify in the log file if it contains the following entry: -``` - Self-testing indicates your ORPort is - reachable from the outside. - Excellent. - Publishing server descriptor. -``` - -About 3 hours after you started your relay it should appear on Metrics portal in Relay Search. - - -#### slide #### -title: More about relays ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Technical tips ----- -description: -- Enable automatic software updates. -- Backup your Tor Identity Keys. -- It’s possible to limit bandwidth usage (and traffic). Check the parameters, for example: AccountingMax, AccountingRule, AccountingStart. -- If run more than one Tor relay, you need to set MyFamily parameter. - - -#### slide #### -title: Orchestrating ----- -description: -- Running multiple relays by hand can be challenging. -- Configuration management tools can make the relay operator life easier: -- Ansible-relayor: [http://github.com/nusenu/ansible-relayor](http://github.com/nusenu/ansible-… -- Bash script: [https://github.com/coldhakca/tor-relay-bootstrap](https://github.com/coldha… - - -#### slide #### -title: Metrics ----- -description: -- Metrics portal - [https://metrics.torproject.org](https://metrics.torproject.org) -- It’s possible to search: how many relays are in the network, how many are exit, etc -- In 2019 there are ~6,600 relays and ~1,500 bridges. -- Check: how many relays are in your country? Who run these relays? How diverse it is? - - -#### slide #### -title: Network diversity ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Monoculture ----- -description: -- A single kernel vulnerability in GNU/Linux impacting Tor relays could be devastating. -- Diversity of Operating System (OS): ~90% of relays are Linux. - - -#### slide #### -title: Monoculture ----- -description: -- Diversity of Autonomous System (AS). Try to avoid the following hosters: OVH SAS (AS16276), Online S.a.s. (AS12876), Hetzner Online GmbH (AS24940), DigitalOcean, LLC (AS14061). - - -#### slide #### -title: More about exit relays ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Legal information ----- -description: -- In many countries there are regulations that exclude communication service providers from liability. -- It's a good idea to consult with a lawyer or your local digital rights organization. -- Under most circumstances you will be able to handle legal matters by having an abuse response letter. - - -#### slide #### -title: Legal resources ----- -description: -- The EFF Tor Legal FAQ: -[https://community.torproject.org/relay/community-resources/eff-tor-legal-faq/](https://community.torproject.org/relay/community-resources/eff-tor-legal-faq/) -- It’s important to respond to abuse complaints in a timely manner (usually within 24 hours). -- Abuse templates letters: -[https://community.torproject.org/relay/community-resources/tor-abuse-templates](https://community.torproject.org/relay/community-resources/tor-abuse-templates) - - -#### slide #### -title: Running relays with others ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Running a relay with others ----- -description: -- You can work with your university department, employer or institution, or an organization like [Torservers.org](Torservers.org) -- [Torservers.org](Torservers.org) is an independent, global network of organizations that helps the Tor network by running high bandwidth Tor relays. -- In many countries operating as a corporation instead of as an individual can also get you certain legal protections. - - -#### slide #### -title: Relays associations ----- -description: -- It’s often advised to create some type of non-profit corporation. This is useful for having a bank account and shared ownership. -- To start a relay association, the most important thing is to have a group of people (3-5 suggested to start) interested in helping. -- For example: Torservers.org, Cold Hak, enn.lu, nos-oignons. - - -#### slide #### -title: Running a relay with universities ----- -description: -- Universities are typically home to a reliable, robust, and well-equipped network. -- Many computer science departments and university libraries run relays, i.e., Massachussetts Institute of Technology (MIT CSAIL), Universitaet Stuttgart, the University of Waterloo. - - -#### slide #### -title: Running a relay with universities ----- -description: -- Start running a relay campaign in your university: [https://www.eff.org/torchallenge/tor-on-campus.html](https://www.eff.org/to… - - -#### slide #### -title: At your company or organization ----- -description: -- If you work at a Tor-friendly company or organization, that's another ideal place to run a relay. -- Companies like Brass Horn Communications, Quintex Alliance Consulting, and OmuraVPN -- And organizations like Digital Courage, Access Now, Derechos Digitales, and Lebanon Libraries in New Hampshire. - - -#### slide #### -title: Bad relays ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: What is a bad relay? ----- -description: -- A bad relay is one that either doesn't work properly or tampers with our users' connections. This can be either through maliciousness or misconfiguration. - - -#### slide #### -title: What is a bad relay? ----- -description: -- For example: tampering with exit traffic in any way (including dropping accepted connections). Or, running HSDirs that harvest and probe .onion addresses - - -#### slide #### -title: Reporting a bad relay ----- -description: -- Bad relays is also a private working group in Tor Project to detect misconfigured, malicious, or suspicious relay. -- Users can report bad relays sending an email to bad-relays(a)lists.torproject.org with the relay's IP address or fingerprint, what kind of behavior did you see, and any additional information it’s needed to reproduce the issue. - - -#### slide #### -title: What happens to bad relays? ----- -description: -- After a relay is reported and we've verified the behavior we'll attempt to contact the relay operator. -- We'll flag it to prevent it from continuing to be used (BadExit, Invalid, Reject). -- The working group actively look for bad relays using open source tools like: exitmap, sysbilhunter. - - -#### slide #### -title: How do I get help running a Tor relay? ----- -layout: title ----- -background-image: /static/images/onion-white.png - - -#### slide #### -title: Getting help ----- -description: -- Read the Tor Relay Guide documentation before: -- [https://torproject.org/relay-guide](https://torproject.org/relay-guide) -- Search the mailing list archive: tor-relays in [https://lists.torproject.org](https://lists.torproject.org) -- Join the IRC channel: #tor-relays in irc.oftc.net - -#### slide #### -title: Thank you! ----- -author: -name - email(a)example.com ----- -subtitle: -PGP FINGERPRINT ----- -layout: title ----- -background-image: /static/images/onion-white.png

1 0

[community/staging] Add and remove content from the slideshow to see if it has any issue with building
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 66923f82e3301ecd3532adbbc429f4971e90e4fa Author: hiro <hiro(a)torproject.org> Date: Wed Mar 24 15:42:23 2021 +0100 Add and remove content from the slideshow to see if it has any issue with building --- content/training/resources/tor-training/contents.lr | 9 --------- 1 file changed, 9 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 875e3a5..d12fdce 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -63,12 +63,3 @@ layout: title background-image: /static/images/onion-white.png --- description: - - -#### slide #### -title: Guard/middle (aka non-exit) relay ----- -description: -- A guard is the first relay in the chain of 3 relays building a Tor circuit. -- A middle relay is neither a guard nor an exit, but acts as the second hop between the two. -- To become a guard, a relay has to be stable and fast (at least 2MByte/s) otherwise it will remain a middle relay.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2021