April 2021 - tor-commits - lists.torproject.org

[depictor/master] Add more known parameters
by tom＠torproject.org 17 Apr '21

17 Apr '21

commit a96f3f2e57801b5fce1921fadf7910513c7a05d5 Author: Tom Ritter <tom(a)ritter.vg> Date: Fri Apr 16 22:52:41 2021 -0400 Add more known parameters --- data/consensus.cfg | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/data/consensus.cfg b/data/consensus.cfg index fd825d4..97232c6 100644 --- a/data/consensus.cfg +++ b/data/consensus.cfg @@ -53,4 +53,6 @@ known_params DoSConnectionEnabled known_params DoSConnectionMaxConcurrentCount known_params hs_service_max_rdv_failures known_params DoSRefuseSingleHopClientRendezvous -known_params sendme_emit_min_version \ No newline at end of file +known_params sendme_emit_min_version +known_params ExtendByEd25519ID +known_params KISTSchedRunInterval \ No newline at end of file

1 0

[depictor/master] Switch stem to be a submodule so I can document what stem version I am using
by tom＠torproject.org 17 Apr '21

17 Apr '21

commit 4aeb834f5565451f8db6b9e9661dc42edc212311 Author: Tom Ritter <tom(a)ritter.vg> Date: Fri Apr 16 22:59:46 2021 -0400 Switch stem to be a submodule so I can document what stem version I am using --- .gitignore | 3 +-- .gitmodules | 6 ++++++ stem | 1 + stem-git | 1 + 4 files changed, 9 insertions(+), 2 deletions(-) diff --git a/.gitignore b/.gitignore index cac3774..25799ba 100644 --- a/.gitignore +++ b/.gitignore @@ -1,8 +1,7 @@ *.pyc *.p *.swp -stem -stem-git + out/index.html out/graphs.html diff --git a/.gitmodules b/.gitmodules new file mode 100644 index 0000000..481d6ca --- /dev/null +++ b/.gitmodules @@ -0,0 +1,6 @@ +[submodule "stem"] + path = stem + url = https://git.torproject.org/stem.git +[submodule "stem-git"] + path = stem-git + url = https://git.torproject.org/stem.git diff --git a/stem b/stem new file mode 120000 index 0000000..9048a37 --- /dev/null +++ b/stem @@ -0,0 +1 @@ +stem-git/stem \ No newline at end of file diff --git a/stem-git b/stem-git new file mode 160000 index 0000000..63a4760 --- /dev/null +++ b/stem-git @@ -0,0 +1 @@ +Subproject commit 63a476056017dda5ede35efc4e4f7acfcc1d7d1a

1 0

[community/staging] Merge branch 'gus-new/community-the-tor-network-update' into 'the-tor-network-update'
by gus＠torproject.org 16 Apr '21

16 Apr '21

commit d2ce15a8906ae4ce62404a7c6042b8e5351c046a Merge: 09073fe 9b2a11a Author: Gus <gus(a)torproject.org> Date: Fri Apr 16 18:33:17 2021 +0000 Merge branch 'gus-new/community-the-tor-network-update' into 'the-tor-network-update' the tor network presentation See merge request gus/community!1 .../training/resources/tor-training/contents.lr | 98 +++++++++------------- 1 file changed, 41 insertions(+), 57 deletions(-)

1 0

[community/staging] Update the training material, removed broken links, added community.tpo reference, grammar review
by gus＠torproject.org 16 Apr '21

16 Apr '21

commit 09073fe2880bb3664da2e9b62c4037e77b9a52a3 Author: gus <gus(a)torproject.org> Date: Wed Apr 14 11:42:54 2021 -0300 Update the training material, removed broken links, added community.tpo reference, grammar review --- .../training/resources/tor-training/contents.lr | 151 +++++++++++---------- 1 file changed, 83 insertions(+), 68 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 8292dd2..08dacbd 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -15,7 +15,7 @@ title: Topics ---- description: -- What' s Tor? +- What's Tor? - Types of relays - Technical setup - More about relays @@ -28,10 +28,10 @@ description: title: What's Tor? ---- description: -- Tor is a free software and an open network -- Mitigates against tracking, surveillance and censorship -- Run by a US non-profit and volunteers from all over the world -- It' s Tor, not TOR +- Tor is a free software and an open network. +- Mitigates against tracking, surveillance and censorship. +- Run by a US non-profit and volunteers from all over the world. +- It's Tor, not TOR. @@ -39,17 +39,17 @@ description: title: The Tor network ---- description: -- An open network, everyone can be part of it. Basically, your server will relay the tor traffic to another server in the Internet. -- The network is composed by different types of servers run by volunteers around the world. -- To ingress in the network, the new server will pass automatically to a new relay lifecycle. +- An open network, everyone can be part of it. Your server will relay the Tor traffic to another server on the Internet. +- The network is composed of different types of servers run by volunteers around the world. +- Before ingressing the network, the server will pass automatically to the relay lifecycle. #### slide #### title: Why run a Tor relay? ---- description: -By running a Tor relay you can help make the Tor network: -- faster (and therefore more usable +By running a Tor relay, you can help make the Tor network: +- faster (and therefore more usable) - more robust against attacks - more stable in case of outages - safer for its users (spying on more relays is harder than on a few) @@ -72,27 +72,27 @@ 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. +- A middle relay is neither a guard nor an exit but acts as the second hop between them. +- To become a guard, a middle 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** +- The exit relay is the final relay in a Tor circuit that sends traffic out its destination. +- That's why exit relays have the most significant legal exposure and liability of all the relays. +- Before running an exit relay, talk 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. +- A bridge is a node in the network that isn't listed in the public Tor directory, making it harder for ISPs and governments to block it. +- Bridges are relatively easy, low-risk, and low bandwidth Tor relays to operate. +- And there's another special kind of bridge: Pluggable transports. It hides your Tor traffic by adding a layer of obfuscation. #### slide #### @@ -100,9 +100,9 @@ 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) +- 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 #### @@ -110,7 +110,6 @@ 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… @@ -129,18 +128,18 @@ description: 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. +- Never run a relay without the consent of the network administrator or machine owner. Read the Terms of Service (ToS) first, so you don’t risk losing 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) +- Read the documentation: [https://community.torproject.org/relay](https://community.torproject.org/re… #### slide #### title: Bandwidth requirements ---- description: -- At least 16 Mbit/s (Mbps) upload and download bandwidth available for Tor. More is better. +- It’s recommended 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. +- If you have less than 10 Mbit/s but at least 1 Mbit/s, we recommend running a bridge with obfs4 support. #### slide #### @@ -148,8 +147,8 @@ 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 +- If you have a metered plan, you might want to configure Tor only to use a given amount of bandwidth or monthly traffic. +- More (>2 TB/month) is better and recommended. #### slide #### @@ -157,7 +156,7 @@ 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. +- 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. @@ -175,14 +174,14 @@ title: Other requirements ---- description: - Any modern CPU should be fine. -- Uptime: Ideally the relay runs on a server which runs 24/7. +- 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 +- Tor community maintain the list GoodBadISPs, about the experience of running relays: https://community.torproject.org/relay/community-resources/good-bad-isps/ - Some providers only allow non-exit relays, so before buying a service, check the GoodBadISPs. @@ -190,7 +189,7 @@ description: title: Choosing your relay hosting ---- description: -- This can cost anywhere between $3.00/mo and thousands per month. +- Runnin a relay can cost anywhere between a few bucks and hundreds per month. #### slide #### @@ -208,7 +207,7 @@ description: title: Non-exit relay - Debian/Ubuntu ---- description: -- Enable the Torproject package repository +- Enable the Tor Project package repository - Install the tor package ``` @@ -299,8 +298,8 @@ description: 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) + +- Optional, but recommended to get package updates faster: [https://community.torproject.org/relay/setup/guard/freebsd/](https://commun… #### slide #### @@ -316,7 +315,7 @@ After restarting the service, verify in the log file if it contains the followin Publishing server descriptor. ``` -About 3 hours after you started your relay it should appear on Metrics portal in Relay Search. +About 3 hours after you started your relay, it should appear on Metrics portal in Relay Search. #### slide #### @@ -336,8 +335,8 @@ 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. +- 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 the MyFamily parameter. #### slide #### @@ -347,7 +346,6 @@ 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 #### @@ -355,9 +353,9 @@ 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? +- It's possible to search: how many relays are in the network, how many are exits, etc. +- In 2021 there are ~6,600 public relays and ~1,500 bridges. +- Check: how many relays are in your country? Who runs these relays? How diverse is it? #### slide #### @@ -383,7 +381,16 @@ description: 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). +- 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: The TorBSD Diversity Project +---- +description: +- The Tor BSD Diversity Project (TDP) is an initiative seeking the BSD Unix operating systems’ use in the network. +- Goals: increase the number of Tor relays running BSDs; Engage the BSD community about Tor anonymity; Port Tor related programs to BSD operating systems. #### slide #### @@ -401,9 +408,9 @@ description: title: Legal information ---- description: -- In many countries there are regulations that exclude communication service providers from liability. +- In many countries, some regulations exclude internet 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. +- Under most circumstances, you will be able to handle legal matters by having an abuse response letter. #### slide #### @@ -412,11 +419,21 @@ title: Legal resources description: - The EFF Tor Legal FAQ: [https://community.torproject.org/relay/community-resources/eff-tor-legal-fa… -- It’s important to respond to abuse complaints in a timely manner (usually within 24 hours). +- 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-templa… +#### slide #### +title: Tips for running an exit relay +---- +description: +- Get a separate IP for the relay, and don’t use it for other services. +- Set up a Tor Exit Notice, so if someone checks your exit IP, they will quickly know that it’s a Tor Exit. +- If you receive excessive complaints, consider running a Reduced Exit Policy. +- For more tips: [https://blog.torproject.org/tips-running-exit-node](https://blog.torproject… + + #### slide #### title: Running relays with others ---- @@ -432,18 +449,16 @@ description: 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. +- You can work with your university department, employer or institution, or an organization like Torservers.org, Nos oignons, etc. +- Some organizations are dedicated to this purpose only, and they are called Relay Associations: [https://community.torproject.org/relay/community-resources/relay-associatio… #### 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. +- It's often advised to create some type of non-profit corporation. This is useful for having a bank account and shared ownership. +- The most important thing is to have a group of people (3-5 suggested to start) interested in helping. #### slide #### @@ -451,14 +466,14 @@ 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. - +- Many computer science departments and university libraries run relays: Massachusetts Institute of Technology, Universität 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… +- Read more: [https://community.torproject.org/relay/community-resources/tor-relay-univer… + #### slide #### @@ -466,8 +481,8 @@ 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. +- Companies like Brass Horn Communications, Quintex Alliance Consulting, and many others. +- And organizations like Digital Courage, Access Now, Derechos Digitales, Calyx Institute, and Lebanon Libraries in New Hampshire. #### slide #### @@ -485,7 +500,7 @@ description: 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. +- A bad relay is one that either doesn't work properly or tampers with our users' connections. That can be either through maliciousness or misconfiguration. #### slide #### @@ -499,17 +514,17 @@ description: 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. +- Bad relays is also a private working group in the Tor Project to detect misconfigured, malicious, or suspicious relay. +- Users can report bad relays by sending an email to bad-relays(a)lists.torproject.org with the relay’s IP address or fingerprint, what kind of behavior you see, and any additional information’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. +- After a relay is reported and verified the behavior, the Tor Project will attempt to contact the relay operator. +- The relay will be flagged to prevent it from being used (BadExit, Invalid, Reject). +- The working group actively looks for bad relays using open source tools like exitmap, sysbilhunter. #### slide #### @@ -527,10 +542,10 @@ description: 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 +- Read the Tor Relay documentation: +- [https://community.torproject.org/relay](https://community.torproject.org/re… +- Subscribe to tor-relays mailing list: [https://lists.torproject.org](https://lists.torproject.org) +- Join our IRC channel: #tor-relays in irc.oftc.net #### slide ####

1 0

[community/staging] the tor network presentation
by gus＠torproject.org 16 Apr '21

16 Apr '21

commit 9b2a11a17033e622894d7a4e6954fa24535f485e Author: emma peel <emmapeel(a)torproject.org> Date: Fri Apr 16 18:33:17 2021 +0000 the tor network presentation --- .../training/resources/tor-training/contents.lr | 98 +++++++++------------- 1 file changed, 41 insertions(+), 57 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 08dacbd..22179c1 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -14,8 +14,7 @@ slides: title: Topics ---- description: - -- What's Tor? +- What is Tor? - Types of relays - Technical setup - More about relays @@ -23,9 +22,8 @@ description: - Getting help - #### slide #### -title: What's Tor? +title: What is Tor? ---- description: - Tor is a free software and an open network. @@ -34,25 +32,25 @@ description: - It's Tor, not TOR. - #### slide #### title: The Tor network ---- description: -- An open network, everyone can be part of it. Your server will relay the Tor traffic to another server on the Internet. +- An open network, everyone can be part of it. - The network is composed of different types of servers run by volunteers around the world. -- Before ingressing the network, the server will pass automatically to the relay lifecycle. +- Your server will relay the Tor traffic to another server on the Internet. +- Before entering the network, your server will automatically go through the relay lifecycle. #### slide #### -title: Why run a Tor relay? +title: Why running a Tor relay? ---- description: By running a Tor relay, you can help make the Tor network: - faster (and therefore more usable) - more robust against attacks - more stable in case of outages -- safer for its users (spying on more relays is harder than on a few) +- safer for users (spying on more relays is harder than on a few) #### slide #### @@ -64,7 +62,6 @@ background_image: /static/images/onion-white.png ---- description: - ----- #### slide #### @@ -72,7 +69,7 @@ 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 them. +- A middle relay is neither a guard nor an exit, but acts as the second hop between them. - To become a guard, a middle relay has to be stable and fast (at least 2MByte/s); otherwise, it will remain a middle relay. @@ -80,8 +77,8 @@ description: title: Exit relay ---- description: -- The exit relay is the final relay in a Tor circuit that sends traffic out its destination. -- That's why exit relays have the most significant legal exposure and liability of all the relays. +- The exit relay is the final relay in a Tor circuit, sends the traffic to its destination. +- That is why exit relays have the most significant legal exposure and liability of all the relays. - Before running an exit relay, talk with your local digital rights organization. - **You should not run a Tor exit relay from your home.** @@ -90,9 +87,9 @@ description: title: Bridge ---- description: -- A bridge is a node in the network that isn't listed in the public Tor directory, making it harder for ISPs and governments to block it. +- A bridge is a node in the network that is not listed in the public Tor directory, making it harder for ISPs and governments to block it. - Bridges are relatively easy, low-risk, and low bandwidth Tor relays to operate. -- And there's another special kind of bridge: Pluggable transports. It hides your Tor traffic by adding a layer of obfuscation. +- And there's another special kind of bridge: Pluggable transport. Hides your Tor traffic by adding a layer of obfuscation. #### slide #### @@ -109,8 +106,8 @@ Non-exit relays pass by a lifecycle of four phases (defined by days): 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). -- Read about all the phases in: [https://blog.torproject.org/lifecycle-new-relay](https://blog.torproject.or… +- After 68 days, if stable and fast enough, the relay will receive a **Guard flag** (steady-state guard phase). +- Read about all the phases in: <https://blog.torproject.org/lifecycle-new-relay> #### slide #### @@ -128,9 +125,10 @@ description: title: Before we start ---- description: -- Never run a relay without the consent of the network administrator or machine owner. Read the Terms of Service (ToS) first, so you don’t risk losing 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://community.torproject.org/relay](https://community.torproject.org/re… +- Never run a relay without the consent of the network administrator or machine owner. + Read the Terms of Service (ToS) first, so you don’t risk losing money. +- Choose which type of relay you will host. A non-exit relay is an easy way to start helping the network. +- Read the documentation: <https://community.torproject.org/relay> #### slide #### @@ -147,7 +145,7 @@ 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 only to use a given amount of bandwidth or monthly traffic. +- If you have a metered plan, you might want to configure Tor to use only a given amount of bandwidth or monthly traffic. - More (>2 TB/month) is better and recommended. @@ -181,15 +179,9 @@ description: title: Choosing your relay hosting ---- description: -- Tor community maintain the list GoodBadISPs, about the experience of running relays: https://community.torproject.org/relay/community-resources/good-bad-isps/ -- Some providers only allow non-exit relays, so before buying a service, check the GoodBadISPs. - - -#### slide #### -title: Choosing your relay hosting ----- -description: -- Runnin a relay can cost anywhere between a few bucks and hundreds per month. +- The Tor community team maintains the list GoodBadISPs, about the experience of running relays: <https://community.torproject.org/relay/community-resources/good-bad-isps/> +- Some providers only allow non-exit relays, so check the GoodBadISPs list before buying a service. +- Running a relay can cost anywhere between a few bucks to hundreds per month. #### slide #### @@ -219,7 +211,7 @@ description: title: Non-exit relay - Debian/Ubuntu ---- description: -- Put the configuration file `/etc/tor/torrc` in place: +- Add relay configuration to the `/etc/tor/torrc` file: ``` Nickname myNiceRelay ExitRelay 0 @@ -257,7 +249,7 @@ description: title: Non-exit relay - FreeBSD ---- description: - - Edit the configuration `file/usr/local/etc/tor/torrc` + - Edit the configuration file `/usr/local/etc/tor/torrc` ``` Nickname myNiceRelay @@ -299,7 +291,7 @@ title: Non-exit relay - FreeBSD ---- description: -- Optional, but recommended to get package updates faster: [https://community.torproject.org/relay/setup/guard/freebsd/](https://commun… +- Optional, but recommended to get package updates faster: <https://community.torproject.org/relay/setup/guard/freebsd/> #### slide #### @@ -336,7 +328,7 @@ 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 the MyFamily parameter. +- If you run more than one Tor relay, you need to set the MyFamily parameter. #### slide #### @@ -345,17 +337,17 @@ 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-… +- Ansible-relayor: <http://github.com/nusenu/ansible-relayor> #### 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 exits, etc. +- Metrics portal: <https://metrics.torproject.org> +- Is possible to search: how many relays are in the network, how many are exits, etc. - In 2021 there are ~6,600 public relays and ~1,500 bridges. -- Check: how many relays are in your country? Who runs these relays? How diverse is it? +- Check: how many relays are in your country? Who runs these relays? How diverse are they? #### slide #### @@ -373,7 +365,7 @@ description: title: Monoculture ---- description: -- A single kernel vulnerability in GNU/Linux impacting Tor relays could be devastating. +- A single kernel vulnerability in GNU/Linux impacting all Tor relays could be devastating. - Diversity of Operating System (OS): ~90% of relays are Linux. @@ -381,7 +373,7 @@ description: title: Monoculture ---- description: -- Diversity of Autonomous System (AS). +- Diversity of Autonomous Systems (AS). - Try to avoid the following hosters: OVH SAS (AS16276), Online S.a.s. (AS12876), Hetzner Online GmbH (AS24940), DigitalOcean, LLC (AS14061). @@ -417,11 +409,9 @@ description: 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/) +- The EFF Tor Legal FAQ: <https://community.torproject.org/relay/community-resources/eff-tor-legal-fa…> - 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) +- Abuse templates letters: <https://community.torproject.org/relay/community-resources/tor-abuse-templa…> #### slide #### @@ -431,7 +421,7 @@ description: - Get a separate IP for the relay, and don’t use it for other services. - Set up a Tor Exit Notice, so if someone checks your exit IP, they will quickly know that it’s a Tor Exit. - If you receive excessive complaints, consider running a Reduced Exit Policy. -- For more tips: [https://blog.torproject.org/tips-running-exit-node](https://blog.torproject… +- For more tips: <https://blog.torproject.org/tips-running-exit-node> #### slide #### @@ -450,14 +440,14 @@ title: Running a relay with others ---- description: - You can work with your university department, employer or institution, or an organization like Torservers.org, Nos oignons, etc. -- Some organizations are dedicated to this purpose only, and they are called Relay Associations: [https://community.torproject.org/relay/community-resources/relay-associatio… +- Some organizations are dedicated to this purpose only, and they are called Relay Associations: <https://community.torproject.org/relay/community-resources/relay-associatio…>. #### 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. +- It's often advised to create some type of non-profit organization. This is useful for having a bank account and shared ownership. - The most important thing is to have a group of people (3-5 suggested to start) interested in helping. @@ -472,7 +462,7 @@ description: title: Running a relay with universities ---- description: -- Read more: [https://community.torproject.org/relay/community-resources/tor-relay-univer… +- Read more: <https://community.torproject.org/relay/community-resources/tor-relay-univer…> @@ -500,7 +490,7 @@ description: title: What is a bad relay? ---- description: -- A bad relay is one that either doesn't work properly or tampers with our users' connections. That can be either through maliciousness or misconfiguration. +- A bad relay is one that either doesn't work properly or tampers with our users' connections. That can be either through maliciousness or misconfiguration. #### slide #### @@ -543,20 +533,14 @@ title: Getting help ---- description: - Read the Tor Relay documentation: -- [https://community.torproject.org/relay](https://community.torproject.org/re… -- Subscribe to tor-relays mailing list: [https://lists.torproject.org](https://lists.torproject.org) + <https://community.torproject.org/relay> +- Subscribe to tor-relays mailing list: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays> - Join our IRC channel: #tor-relays in irc.oftc.net #### slide #### title: Thank you! ---- -author: -name - email(a)example.com ----- -subtitle: -PGP FINGERPRINT ----- slide_layout: title-slide ---- background_image: /static/images/onion-white.png

1 0

[community/staging] Merge branch 'update-slideshow-tor-network' into staging
by gus＠torproject.org 16 Apr '21

16 Apr '21

commit 809818d7ef75ec7761b6091de0abf257ad867340 Merge: 4b278ad d2ce15a Author: gus <gus(a)torproject.org> Date: Fri Apr 16 15:46:26 2021 -0300 Merge branch 'update-slideshow-tor-network' into staging .../training/resources/tor-training/contents.lr | 199 ++++++++++----------- 1 file changed, 99 insertions(+), 100 deletions(-)

1 0

[gettor-web/translations] remove uppercase and capitalization styling, for l10n
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit 1be5aaab2f2f24fd3a142512b0b2f47bbd73408d Author: emma peel <emma.peel(a)riseup.net> Date: Mon Apr 12 11:00:22 2021 +0200 remove uppercase and capitalization styling, for l10n --- templates/layout.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/templates/layout.html b/templates/layout.html index 76871a1..bc61f5f 100644 --- a/templates/layout.html +++ b/templates/layout.html @@ -12,10 +12,10 @@ <div class="row"> <div class="col-12 content-center pt-5"> <div class="row"> - <h6 class="mx-auto text-white text-uppercase">{% block section %}{{ this.section }}{% endblock %}</h6> + <h6 class="mx-auto text-white">{% block section %}{{ this.section }}{% endblock %}</h6> </div> <div class="row pb-5"> - <h2 class="mx-auto display-3 text-white text-capitalize">{% block title %}{{ this.title }}{% endblock %}</h2> + <h2 class="mx-auto display-3 text-white">{% block title %}{{ this.title }}{% endblock %}</h2> </div> </div> </div>

1 0

[translation/tpo-web] https://gitweb.torproject.org/translation.git/commit/?h=tpo-web
by translation＠torproject.org 16 Apr '21

16 Apr '21

commit 00958e6265aa12f236463a84e3ff0c62b347cc4b Author: Translation commit bot <translation(a)torproject.org> Date: Fri Apr 16 17:47:48 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tpo-web --- contents+my.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contents+my.po b/contents+my.po index 9989e7e442..e4e1440071 100644 --- a/contents+my.po +++ b/contents+my.po @@ -128,7 +128,7 @@ msgstr "ဘလော့ဂ်" #: https//www.torproject.org/menu/ (content/menu/contents+en.lrpage.body) msgid "Donate" -msgstr "Donate" +msgstr "" #: https//www.torproject.org/menu/ (content/menu/contents+en.lrpage.body) msgid "Donate Now"

1 0

[gettor-web/translations] add Burmese to preview
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit 7bb806193020b09f6f5e5c74266c5654b5a7519a Author: emma peel <emma.peel(a)riseup.net> Date: Fri Apr 16 19:46:11 2021 +0200 add Burmese to preview --- GetTor.lektorproject | 5 +++++ configs/i18n.ini | 2 +- databags/alternatives.ini | 6 ++++++ 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/GetTor.lektorproject b/GetTor.lektorproject index 7d43bf9..ce80d9f 100644 --- a/GetTor.lektorproject +++ b/GetTor.lektorproject @@ -65,6 +65,11 @@ name = Macedonian (mk) url_prefix = /mk/ locale = mk +[alternatives.my] +name = မြန်မာ (my) +url_prefix = /my/ +locale = my + [alternatives.pl] name = Polski (pl) url_prefix = /pl/ diff --git a/configs/i18n.ini b/configs/i18n.ini index 130e206..70bc908 100644 --- a/configs/i18n.ini +++ b/configs/i18n.ini @@ -1,5 +1,5 @@ content = en -translations = ar,de,el,es,fa,fr,he,id,it,ka,mk,pl,pt-BR,sq,tr,zh-CN +translations = ar,de,el,es,fa,fr,he,id,it,ka,mk,my,pl,pt-BR,sq,tr,zh-CN i18npath = i18n translate_paragraphwise = False url_prefix = https://gettor.torproject.org/ diff --git a/databags/alternatives.ini b/databags/alternatives.ini index 02f69ab..2780672 100644 --- a/databags/alternatives.ini +++ b/databags/alternatives.ini @@ -70,6 +70,12 @@ order = order-last language = македонски (mk) url = /mk/ +[my] +direction = text-left +order = order-last +language = မြန်မာ (my) +url = /my/ + [pl] direction = text-left order = order-last

1 0

[tor-browser-build/maint-10.0-desktop] Release preparation for 10.0.16
by sysrqb＠torproject.org 16 Apr '21

16 Apr '21

commit 67473253d678b22f0102dac6c370c8ac38e1048d Author: Matthew Finkel <sysrqb(a)torproject.org> Date: Thu Apr 15 03:49:57 2021 +0000 Release preparation for 10.0.16 Versions bump and Changelog update --- projects/firefox/config | 4 ++-- projects/tor-browser/Bundle-Data/Docs/ChangeLog.txt | 8 ++++++++ projects/tor-browser/config | 4 ++-- projects/tor-launcher/config | 2 +- rbm.conf | 4 ++-- 5 files changed, 15 insertions(+), 7 deletions(-) diff --git a/projects/firefox/config b/projects/firefox/config index 22b491c..e5baf06 100644 --- a/projects/firefox/config +++ b/projects/firefox/config @@ -1,14 +1,14 @@ # vim: filetype=yaml sw=2 version: '[% c("abbrev") %]' filename: 'firefox-[% c("version") %]-[% c("var/osname") %]-[% c("var/build_id") %]' -git_hash: 'tor-browser-[% c("var/firefox_version") %]-[% c("var/torbrowser_branch") %]-1-build3' +git_hash: 'tor-browser-[% c("var/firefox_version") %]-[% c("var/torbrowser_branch") %]-1-build1' tag_gpg_id: 1 git_url: https://git.torproject.org/tor-browser.git git_submodule: 1 gpg_keyring: torbutton.gpg var: - firefox_platform_version: 78.9.0 + firefox_platform_version: 78.10.0 firefox_version: '[% c("var/firefox_platform_version") %]esr' torbrowser_branch: 10.0 branding_directory: 'browser/branding/alpha' diff --git a/projects/tor-browser/Bundle-Data/Docs/ChangeLog.txt b/projects/tor-browser/Bundle-Data/Docs/ChangeLog.txt index 924c893..59c6316 100644 --- a/projects/tor-browser/Bundle-Data/Docs/ChangeLog.txt +++ b/projects/tor-browser/Bundle-Data/Docs/ChangeLog.txt @@ -1,3 +1,11 @@ +Tor Browser 10.0.16 -- April 20 2021 + * Windows + OS X + Linux + * Update Firefox to 78.10.0esr + * Update NoScript to 11.2.4 + * Bug 40007: Update domain fronting config for Moat [tor-launcher] + * Bug 40390: Add Burmese as a new locale [tor-browser] + * Bug 40408: Disallow SVG Context Paint in all web content [tor-browser] + Tor Browser 10.0.15 -- March 26 2021 * Windows + OS X + Linux * Update Openssl to 1.1.1k diff --git a/projects/tor-browser/config b/projects/tor-browser/config index 20d920d..2c4575c 100644 --- a/projects/tor-browser/config +++ b/projects/tor-browser/config @@ -77,9 +77,9 @@ input_files: enable: '[% c("var/snowflake") && ! c("var/android") %]' - filename: Bundle-Data enable: '[% ! c("var/android") %]' - - URL: https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suit… + - URL: https://addons.cdn.mozilla.net/user-media/addons/722/noscript_security_suit… name: noscript - sha256sum: eafc5f5be40d33a34d757940b5391455dad166921c880ee67daab056078d51ae + sha256sum: 278ee526d7c3ce5236c1a04aa5b6605c81b82399b846e43cdf6f93f11fef1ec9 - filename: 'RelativeLink/start-tor-browser.desktop' enable: '[% c("var/linux") %]' - filename: 'RelativeLink/execdesktop' diff --git a/projects/tor-launcher/config b/projects/tor-launcher/config index 0c9698a..1ebf3e1 100644 --- a/projects/tor-launcher/config +++ b/projects/tor-launcher/config @@ -1,5 +1,5 @@ # vim: filetype=yaml sw=2 -version: 0.2.26 +version: 0.2.28 git_url: https://git.torproject.org/tor-launcher.git git_hash: '[% c("version") %]' gpg_keyring: torbutton.gpg diff --git a/rbm.conf b/rbm.conf index 56f2cd7..e40f731 100644 --- a/rbm.conf +++ b/rbm.conf @@ -24,11 +24,11 @@ buildconf: git_signtag_opt: '-s' var: - torbrowser_version: '10.0.15' + torbrowser_version: '10.0.16' torbrowser_build: 'build1' torbrowser_incremental_from: - - 10.0.12 - 10.0.14 + - 10.0.15 project_name: tor-browser multi_lingual: 0 build_mar: 1

1 0