tor-commits March 2021

tor-commits@lists.torproject.org

17 participants
2169 discussions

[community/staging] Finish template and slides
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 795bfd57083bc5ed2cff0259b35b3d688e90d664 Author: hiro <hiro(a)torproject.org> Date: Mon Mar 15 20:04:58 2021 +0100 Finish template and slides --- assets/static/revealjs/dist/theme/tor.css | 6 +- .../training/resources/tor-training/contents.lr | 400 +++++++++++++++++++-- templates/blocks/slide.html | 3 +- 3 files changed, 382 insertions(+), 27 deletions(-) diff --git a/assets/static/revealjs/dist/theme/tor.css b/assets/static/revealjs/dist/theme/tor.css index 2c55510..0ff2e67 100644 --- a/assets/static/revealjs/dist/theme/tor.css +++ b/assets/static/revealjs/dist/theme/tor.css @@ -301,8 +301,12 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba *********************************************/ @media print { .backgrounds { - background-color: #fff; } } + background-color: #fff; } +} +.print-pdf .footer { + display: none; +} /********************************************* * FOOTER *********************************************/ diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 16254df..4a38efa 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -22,8 +22,7 @@ description: - Relay diversity - Getting help ----- -background: white + #### slide #### title: What's Tor? @@ -34,8 +33,7 @@ description: - Run by a US non-profit and volunteers from all over the world - It' s Tor, not TOR ----- -background: white + #### slide #### title: The Tor network @@ -44,8 +42,7 @@ 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. ----- -background: white + #### slide #### title: Why run a Tor relay? @@ -56,8 +53,7 @@ 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) ----- -background: white + #### slide #### title: Types of Relays @@ -66,6 +62,7 @@ layout: title ---- background-image: /static/images/onion-white.png + #### slide #### title: Guard/middle (aka non-exit) relay ---- @@ -73,8 +70,7 @@ 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. ----- -background: white + #### slide #### title: Exit relay @@ -84,8 +80,7 @@ description: - 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** ----- -background: white + #### slide #### title: Bridge @@ -94,8 +89,7 @@ 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. ----- -background: white + #### slide #### title: The lifecycle of a new relay @@ -105,8 +99,7 @@ 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) ----- -background: white + #### slide #### title: The lifecycle of a new relay @@ -115,8 +108,7 @@ 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… ----- -background: white + #### slide #### title: Relay requirements @@ -125,6 +117,7 @@ layout: title ---- background-image: /static/images/onion-white.png + #### slide #### title: Before we start ---- @@ -132,8 +125,7 @@ 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) ----- -background: white + #### slide #### title: Bandwidth requirements @@ -142,8 +134,7 @@ 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. ----- -background: white + #### slide #### title: Monthly outbound traffic @@ -152,8 +143,7 @@ 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 ----- -background: white + #### slide #### title: Public IPv4 address @@ -163,5 +153,365 @@ description: - 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 ---- -background: white +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 diff --git a/templates/blocks/slide.html b/templates/blocks/slide.html index e0421ea..809873c 100644 --- a/templates/blocks/slide.html +++ b/templates/blocks/slide.html @@ -3,9 +3,10 @@ <h3>{{ this.title }}</h3> <hr class="dark" /> <h4>{{ this.subtitle }}</h4> + <h5>{{ this.author }}</h5> </section> {% else %} -<section data-background-color="{{ this.background }}"> +<section {% if this.background != "white" %} data-background-color="{{ this.background }}" {% else %} data-background-color="white" {% endif %} > <h2>{{ this.title }}</h2> {{ this.description }}

1 0

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

21 Mar '21

commit 62bc0a3a324c3f40002d3578b6b339523f727c6e Author: hiro <hiro(a)torproject.org> Date: Sun Mar 21 20:06:09 2021 +0100 Use string for localization --- content/outreach/contents.lr | 2 +- templates/hero.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) 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 --- diff --git a/templates/hero.html b/templates/hero.html index f02d70c..5c215c8 100644 --- a/templates/hero.html +++ b/templates/hero.html @@ -2,7 +2,7 @@ <div class="row"> <div class="col-12 content-center"> <div class="row"> - <h6 class="mx-auto text-white pt-3">{{ _(Community) }}</h6> + <h6 class="mx-auto text-white pt-3">{{ _('Community') }}</h6> </div> <div class="row"> <h2 class="mx-auto display-3 text-white">{% block title %}{{ this.title }}{% endblock %}</h2>

1 0

[community/staging] Add ASN to Axtel
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 1e6f286391a5727c97186757fa54a38e32e78e77 Author: Jacobo <jacobo(a)metahumano.org> Date: Sat Aug 8 23:21:40 2020 -0500 Add ASN to Axtel --- content/relay-operations/community-resources/good-bad-isps/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 69e5c5e..1bc19bc 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -151,7 +151,7 @@ For network diversity and stronger anonymity, you should avoid providers and cou | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| Axtel | - | Yes | Yes | Yes | Currently some Guard / Middle and exit nodes are running in Axtel network | 2019 | +| Axtel | AS6503 | Yes | Yes | Yes | Currently some Guard / Middle and exit nodes are running in Axtel network | 2019 | ### Moldova

1 0

[community/staging] Add Mega Cable to Good Experiences ISP in Mexico
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 80d275af4c3d8594dad6e038b630c161c8287310 Author: Jacobo <jacobo(a)metahumano.org> Date: Wed Aug 12 16:56:25 2020 -0500 Add Mega Cable to Good Experiences ISP in Mexico --- content/relay-operations/community-resources/good-bad-isps/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index e6097af..504fb26 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -153,7 +153,7 @@ For network diversity and stronger anonymity, you should avoid providers and cou |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| | Axtel | AS6503 | Yes | Yes | Yes | Currently some Guard / Middle and exit nodes are running in Axtel network | 2020 | | Telmex | AS8151 | No | Yes | No | Currently some Guard / Middle nodes are running in Telmex network | 2020 | - +| Mega Cable | AS13999 | No | Yes | No | Currently some Guard / Middle nodes are running in Mega Cable network | 2020 | ### Moldova

1 0

[community/staging] Add Telmex to Good Experiences in Mexico and update Axtel
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 234106cdb7eb56ba44a2b9b0b3e270da6b239b4a Author: Jacobo <jacobo(a)metahumano.org> Date: Sat Aug 8 23:24:18 2020 -0500 Add Telmex to Good Experiences in Mexico and update Axtel --- .../relay-operations/community-resources/good-bad-isps/contents.lr | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 1bc19bc..e6097af 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -151,7 +151,9 @@ For network diversity and stronger anonymity, you should avoid providers and cou | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| Axtel | AS6503 | Yes | Yes | Yes | Currently some Guard / Middle and exit nodes are running in Axtel network | 2019 | +| Axtel | AS6503 | Yes | Yes | Yes | Currently some Guard / Middle and exit nodes are running in Axtel network | 2020 | +| Telmex | AS8151 | No | Yes | No | Currently some Guard / Middle nodes are running in Telmex network | 2020 | + ### Moldova

1 0

[community/staging] Refine Windows bridge instructions
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 25f93cb11a266b8feab6498e753b89ed20008065 Author: Nicolei Ocana <nicoleiocana(a)gmail.com> Date: Wed Jul 15 00:35:17 2020 +0000 Refine Windows bridge instructions --- content/relay-operations/technical-setup/bridge/windows/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/windows/contents.lr b/content/relay-operations/technical-setup/bridge/windows/contents.lr index 8de2601..7bf3ddc 100644 --- a/content/relay-operations/technical-setup/bridge/windows/contents.lr +++ b/content/relay-operations/technical-setup/bridge/windows/contents.lr @@ -16,7 +16,7 @@ body: * [Windows Expert Bundle](https://www.torproject.org/download/tor/). Unzip the contents on the desktop. -* [Tor Browser](https://www.torproject.org/download/#windows). Run the `.exe` and install with default settings. +* [Tor Browser (version depends on your computer)](https://www.torproject.org/download/languages/). Run the `.exe` and install with default settings. You will need to show hidden items and file name extensions. In your Explorer window, in the top-left, click on the View tab. In the Show/hide section furthest to the right, check the checkbox for Hidden items; check the checkbox for File name extensions.

1 0

[community/staging] Changed exit nodes in Axtel to yes
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit c577dd9b86bee5312b4304618dfb9d14940d6ae5 Author: Jacobo <jacobo(a)metahumano.org> Date: Sat Aug 8 23:19:34 2020 -0500 Changed exit nodes in Axtel to yes --- content/relay-operations/community-resources/good-bad-isps/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 4dab46e..69e5c5e 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -151,7 +151,7 @@ For network diversity and stronger anonymity, you should avoid providers and cou | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| -| Axtel | - | Yes | Yes | ? | Currently some Guard / Middle nodes are running in Axtel network | 2019 | +| Axtel | - | Yes | Yes | Yes | Currently some Guard / Middle and exit nodes are running in Axtel network | 2019 | ### Moldova

1 0

[community/staging] Add CC documents links in homepage.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 90e80e8d25aafe6cc664b005743e2727dd74359b Author: antonela <antonela(a)torproject.org> Date: Tue Jul 21 08:54:32 2020 -0300 Add CC documents links in homepage. Close https://gitlab.torproject.org/tpo/web/community/-/issues/141 --- templates/homepage.html | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/templates/homepage.html b/templates/homepage.html index 9f7db9e..d01c9ff 100644 --- a/templates/homepage.html +++ b/templates/homepage.html @@ -19,7 +19,13 @@ </main> </div> </div> - </div> + <div class="container"> + <div class="row p-5 m-3 border"> + <p> + {{ _('The Tor Project is committed to fostering an inclusive environment and community. Tor is a place where people should feel safe to engage, share their point of view, and participate.') }} Read our <a href="https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.t…" title="Code of Conduct" target="_blank">Code of Conduct</a>, <a href="https://gitweb.torproject.org/community/policies.git/tree/social_contract.t…" title="Social Contract" target="_blank">Social Contract</a>, <a href="https://gitweb.torproject.org/community/policies.git/tree/statement_of_valu…" title="Statement of Values" target="_blank">Statement of Values</a> and learn about the <a href="https://gitweb.torproject.org/community/policies.git/tree/community_council…" title="Tor Commmunity Council" target="_blank">Tor Community Council</a>. + </p> + </div> + </div> <footer> {% include 'footer.html' %} </footer>

1 0

[community/staging] Change whitelist to allow, change blacklist to blocklist
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit a061237a03aa63b3551459e172faf01ac611ce6d Author: gus <gus(a)torproject.org> Date: Tue Jul 21 16:17:20 2020 -0400 Change whitelist to allow, change blacklist to blocklist --- content/relay-operations/community-resources/bad-relays/contents.lr | 2 +- .../relay-operations/technical-setup/bridge/dragonflybsd/contents.lr | 2 +- content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 2 +- content/relay-operations/technical-setup/bridge/netbsd/contents.lr | 2 +- content/relay-operations/types-of-relays/contents.lr | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/relay-operations/community-resources/bad-relays/contents.lr b/content/relay-operations/community-resources/bad-relays/contents.lr index 0a03c6f..13dcdc9 100644 --- a/content/relay-operations/community-resources/bad-relays/contents.lr +++ b/content/relay-operations/community-resources/bad-relays/contents.lr @@ -19,7 +19,7 @@ A bad relay is one that either doesn't work properly or tampers with our users' * Performing a [Sybil attack](https://en.wikipedia.org/wiki/Sybil_attack), which means flooding the network with new relays in an effort to deanonymize users. If you want to run multiple relays then that's great! But please be sure to set the [MyFamily parameter](https://www.torproject.org/docs/tor-manual.html.en#MyFamily). * Exit relays routing their exit traffic back into the tor network (not actually exiting any traffic) -Also, if your relay is stolen or goes missing, please report it as well, so we can blacklist it in case whoever took it puts it back online. +Also, if your relay is stolen or goes missing, please report it as well, so we can blocklist it in case whoever took it puts it back online. The following are currently permitted yet do have some discussion for prohibition (as such, they should not be reported at this time)... diff --git a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr index b12ef7e..22d58ad 100644 --- a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr @@ -103,7 +103,7 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, * 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**. +* Are you firewalling your DragonflyBSD? If so, make sure that `obfs4proxy` can talk to `tor` over the loopback interface - do not forget to allow the **ExtORPort**. ### 4. Start `tor`: diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 93f7aec..073fb68 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -54,7 +54,7 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, * 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 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 using FreeBSD's firewall with a "default deny" policy? If so, make sure that your obfs4proxy can talk to your Tor process over the loopback interface. Don't forget to whitelist Tor's `ExtORPort`. +* Are you using FreeBSD's firewall with a "default deny" policy? If so, make sure that your obfs4proxy can talk to your Tor process over the loopback interface. Don't forget to allow Tor's `ExtORPort`. ### 3. Ensure that the `random_id` sysctl setting is enabled: diff --git a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr index 91eb156..a9799cd 100644 --- a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr @@ -60,7 +60,7 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, * 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**. +* Are you firewalling your NetBSD? If so, make sure that `obfs4proxy` can talk to `tor` over the loopback interface - do not forget to allow the **ExtORPort**. ### 3. Start `tor`: diff --git a/content/relay-operations/types-of-relays/contents.lr b/content/relay-operations/types-of-relays/contents.lr index dccab39..3dc30aa 100644 --- a/content/relay-operations/types-of-relays/contents.lr +++ b/content/relay-operations/types-of-relays/contents.lr @@ -55,7 +55,7 @@ If you are considering running an exit relay, please read the [section on legal # Bridge The design of the Tor network means that the IP address of Tor relays is public. -However, one of the ways Tor can be blocked by governments or ISPs is by blacklisting the IP addresses of these public Tor nodes. +However, one of the ways Tor can be blocked by governments or ISPs is by blocklisting the IP addresses of these public Tor nodes. Tor bridges are nodes in the network that are not listed in the public Tor directory, which make it harder for ISPs and governments to block them. Bridges are useful for Tor users under oppressive regimes or for people who want an extra layer of security because they're worried somebody will recognize that they are contacting a public Tor relay IP address.

1 0

[community/staging] Update dead links
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 5666dcdfe8172d32c40eb15ba4e8b62c66cd75a4 Author: Gustavo Gus <gusgustavo(a)users.noreply.github.com> Date: Fri Aug 14 18:11:15 2020 +0000 Update dead links --- content/relay-operations/community-resources/bad-relays/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/relay-operations/community-resources/bad-relays/contents.lr b/content/relay-operations/community-resources/bad-relays/contents.lr index 13dcdc9..7ccfca5 100644 --- a/content/relay-operations/community-resources/bad-relays/contents.lr +++ b/content/relay-operations/community-resources/bad-relays/contents.lr @@ -35,7 +35,7 @@ You can check which exit you are using at any time by visiting [tor check](https 2. What kind of behavior did you see? 3. Any additional information we'll need to reproduce the issue. -However, if you need help with anything Tor-related, please contact the [help desk](https://www.torproject.org/about/contact) instead. +However, if you need help with anything Tor-related, please contact the [front desk](https://www.torproject.org/about/contact) instead. ### What happens to bad relays? @@ -57,7 +57,7 @@ In just about all cases we're unable to contact the operator to resolve the issu Yes. For our automated issue detection see [exitmap](http://www.cs.kau.se/philwint/spoiled_onions/) and [sybilhunter](https://gitweb.torproject.org/user/phw/sybilhunter.git/). -Other monitors include [tortunnel](http://www.thoughtcrime.org/software/tortunnel/), [SoaT](https://gitweb.torproject.org/torflow.git/blob/HEAD:/NetworkScanners/…, [torscanner](https://code.google.com/p/torscanner/), and [DetecTor](http://detector.io/DetecTor.html). +Other monitors include [tortunnel](https://github.com/moxie0/tortunnel), [SoaT](https://gitweb.torproject.org/torflow.git/tree/NetworkScanners/ExitAu…, [torscanner](https://code.google.com/p/torscanner/), and DetecTor. ---

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2021