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

[community/staging] Merge remote-tracking branch 'goodiec/patch-1'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit b21d2b5d3eebc00077e14bb5674bb9d7a01082a6 Merge: 38a039d 4518f47 Author: emma peel <emma.peel(a)riseup.net> Date: Thu Mar 18 16:38:43 2021 +0100 Merge remote-tracking branch 'goodiec/patch-1' will-close: https://gitlab.torproject.org/tpo/web/community/-/issues/158 content/localization/translation-problem/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

1 0

[community/staging] Update training resources and add private bridge workshop
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit cc0e9dce78d5455256471372816700b3b8557739 Author: gus <gus(a)torproject.org> Date: Tue Mar 16 20:22:29 2021 -0300 Update training resources and add private bridge workshop --- databags/training-resources.json | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/databags/training-resources.json b/databags/training-resources.json index f1e8b10..ba7f3ea 100644 --- a/databags/training-resources.json +++ b/databags/training-resources.json @@ -4,9 +4,9 @@ "label" : "All About Tor", "name" : "all-about-tor", "filename" : "all-about-tor-full-pack", - "formats" : ["odp","md"], + "formats" : ["odp","pdf"], "description" : "Full set of slides for Tor Trainings", - "date" : "2019" + "date" : "2021" }, "todo sobre tor" : @@ -27,5 +27,15 @@ "formats" : ["odp","pdf"], "description" : "Learn about the Tor network and how to run a relay", "date" : "2019" + }, + + "Private bridges workshop" : + { + "label" : "Running Tor bridges", + "name" : "private-bridges", + "filename" : "private-bridges-workshop", + "formats" : ["odp","pdf"], + "description" : "Learn how to run a private unlisted Tor bridge", + "date" : "2021" } }

1 0

[community/staging] Remove tor-training slideslow
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit a67cffe05596b199dad831ca137ccf1702d073d5 Author: hiro <hiro(a)torproject.org> Date: Mon Mar 15 18:13:38 2021 +0100 Remove tor-training slideslow --- .../training/resources/tor-training/contents.lr | 167 --------------------- 1 file changed, 167 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr deleted file mode 100644 index 16254df..0000000 --- a/content/training/resources/tor-training/contents.lr +++ /dev/null @@ -1,167 +0,0 @@ -_model: slideshow ---- -title: The Tor Network ---- -_template: slideshow.html ---- -background: white ---- -image: /static/images/onion.png ---- -slides: - -#### slide #### -title: Topics ----- -description: - -- What' s Tor? -- Types of relays -- Technical setup -- More about relays -- Relay diversity -- Getting help - ----- -background: white - -#### slide #### -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 - ----- -background: white - -#### slide #### -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. ----- -background: white - -#### 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 -- 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 ----- -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. ----- -background: white - -#### 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** ----- -background: white - -#### 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. ----- -background: white - -#### 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) ----- -background: white - -#### 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… ----- -background: white - -#### 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) ----- -background: white - -#### 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. ----- -background: white - -#### 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 ----- -background: white - -#### 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. ----- -background: white

1 0

[community/staging] updating section open user research content/user-research/open/contents.lr
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 38a039de7d2471e0dc4233f33a446621d5b20576 Author: nah <nah(a)riseup.net> Date: Wed Mar 17 10:30:29 2021 -0300 updating section open user research content/user-research/open/contents.lr Apply 1 suggestion(s) to 1 file(s) adding a pipe --- content/user-research/open/contents.lr | 38 ++++++++++++++++++++-------------- 1 file changed, 22 insertions(+), 16 deletions(-) diff --git a/content/user-research/open/contents.lr b/content/user-research/open/contents.lr index c1f5c1a..813cde3 100644 --- a/content/user-research/open/contents.lr +++ b/content/user-research/open/contents.lr @@ -17,31 +17,37 @@ key: 2 html: two-columns-page.html --- body: + These are our current needs for testing Tor products, as well as methodologies and testing scripts. Before running Tor user research, be sure you read our [Guidelines to becoming a user researcher with Tor](https://community.torproject.org/user-research/guidelines). ### Tor Browser for Desktop -* [User Research: Onboarding](https://dip.torproject.org/torproject/ux/research/blob/master/s… -* [User Research: Security Settings](https://dip.torproject.org/torproject/ux/research/blob/master/scr… -* User Research: New Identity -* [User Needs Discovery](https://dip.torproject.org/torproject/ux/research/blob/master/sc… +* [Tor Browser Usage](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%… +* [User Research: Onboarding](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scr… +* [Discovery: Get Bridges](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/script… +* [User Needs Discovery](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scri… ### Tor Browser for Android -* [User Research: Onboarding](https://dip.torproject.org/torproject/ux/research/blob/master/s… -* User Research: Security Settings -* User Research: New Identity -* [User Needs Discovery](https://dip.torproject.org/torproject/ux/research/blob/master/sc… +* [Tor Browser Usage](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%… +* [User Research: Onboarding](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scr… +* [User Needs Discovery](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scri… + +### Emma +* [Run Emma Network Test](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%2… + +### Other Research +* [Censored Continent: Understanding the use of tools during Internet censorship in Africa: Cameroon, Nigeria, Uganda and Zimbabwe as case studies.](https://research.torproject.org/techreports/icfp-censored-contine… -### Onion Services -* User Research: Onion Security Indicator ## Past User Research We’re committed to open design, so you can see the user research we’ve conducted in the global-south. If you want to run user research with us, please [get in touch.](https://lists.torproject.org/cgi-bin/mailman/listinfo/ux) | Project | Methodology | Locations | Dates | Reporting | | -------- | ----------- | --------- | --------- | ----- | -| Tor Launcher | Usability testing ([.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/scripts%20and%20activities/2018/1.India_User_testing_Tor_Launcher_Test.pdf)) | Mumbai(IN) | Q118 | .pdf | -| Onion Security Indicator | Usability testing ([.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/scripts%20and%20activities/2018/2.User_testing_.onion_states_Test.pdf)) | Mumbai(IN), Kampala(UG), Valencia(ES), Mombasa(KE)| Q118, Q218 | [.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/reports/2018/ur_kenya_2018_Feature_report__Onions_and_Circuit_Display.pdf) | -| TB Circuit Display | Usability testing ([.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/scripts%20and%20activities/2018/3.User_testing_circuit_display_Test.pdf)) | Kampala(UG), Nairobi(KE), Mombasa(KE) | Q118, Q218 | [.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/reports/2018/ur_kenya_2018_Feature_report__Onions_and_Circuit_Display.pdf) | -| Tor Browser for Desktop | User needs discovery ([.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/scripts%20and%20activities/2018/4.00_user_needs_discovery.pdf)) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | [.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/reports/2018/ur_colombia_2018_report_tbb-tba.pdf) | -| Tor Browser for Android | User needs discovery ([.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/scripts%20and%20activities/2018/4.00_user_needs_discovery.pdf)) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | [.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/reports/2018/ur_colombia_2018_report_tbb-tba.pdf) | -| Tor Users Demographics | Survey ([.pdf](https://dip.torproject.org/torproject/ux/research/blob/master/scripts%20and%20activities/2018/6.Spanish_-_Tor_Project_Survey_-_Tor_Users_Demographics.pdf)) | Online | 2018 | .pdf | +| Discovery: Get Bridges | User Discovery ([.md](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2020/discovery-bridges.md)) | Online | Q420, Q121 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2021/User_Research_-_Bridges.pdf) | +| Tor Users Demographics | Survey ([.md](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2020/user_demographics-en.md)) | Online | 2020 | n/a | +| User Research: Security Settings | Usability testing ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2019/2.Tor_Browser_Desktop_-_Security_Settings.pdf)) | Multiple locations | 2019 | n/a | +| Tor Launcher | Usability testing ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/1.India_User_testing_Tor_Launcher_Test.pdf)) | Mumbai(IN) | Q118 | .pdf | +| Onion Security Indicator | Usability testing ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/2.User_testing_.onion_states_Test.pdf)) | Mumbai(IN), Kampala(UG), Valencia(ES), Mombasa(KE)| Q118, Q218 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2018/ur_kenya_2018_Feature_report__Onions_and_Circuit_Display.pdf) | +| TB Circuit Display | Usability testing ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/3.User_testing_circuit_display_Test.pdf)) | Kampala(UG), Nairobi(KE), Mombasa(KE) | Q118, Q218 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2018/ur_kenya_2018_Feature_report__Onions_and_Circuit_Display.pdf) | +| Tor Browser for Desktop | User needs discovery ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/4.00_user_needs_discovery.pdf)) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2018/ur_colombia_2018_report_tbb-tba.pdf) | +| Tor Browser for Android | User needs discovery ([.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/scripts%20and%20activities/2018/4.00_user_needs_discovery.pdf)) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | [.pdf](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/reports/2018/ur_colombia_2018_report_tbb-tba.pdf) |

1 0

[community/staging] clarify reverse DNS advice
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit f0b95049ba862bba074b72e1007663d6de2906de Author: anarcat <anarcat(a)torproject.org> Date: Mon Mar 15 14:56:36 2021 +0000 clarify reverse DNS advice We sometimes receive complaints we can't do anything about to abuse(a)torproject.org because people use the domain in the reverse DNS. This should be avoided because we (the torproject.org) are not actually responsible for the relays themselves. --- content/relay-operations/technical-setup/exit/contents.lr | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/relay-operations/technical-setup/exit/contents.lr b/content/relay-operations/technical-setup/exit/contents.lr index 69c19fc..5b17ec7 100644 --- a/content/relay-operations/technical-setup/exit/contents.lr +++ b/content/relay-operations/technical-setup/exit/contents.lr @@ -26,6 +26,8 @@ Before turning your non-exit relay into an exit relay, ensure that you have set If your provider offers it, make sure your WHOIS record contains clear indications that this is a Tor exit relay. +Do use a domain name that you own. Definitely do not use `torproject.org` as a domain name for your reverse DNS. + ## Exit Notice HTML page To make it even more obvious that this is a Tor exit relay you should serve a Tor exit notice HTML page.

1 0

[community/staging] Fix typo
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 0c630870c1266286fc503123f0d0c741d18a366c Author: hiro <hiro(a)torproject.org> Date: Tue Mar 23 17:57:18 2021 +0100 Fix typo --- lego | 2 +- templates/hero.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lego b/lego index 4cb4064..842b8e9 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 4cb4064486b300f04573b4dde54afa6835dafa63 +Subproject commit 842b8e924653b41b382d9a26eb33ecb4f4638553 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] Fix "restart tor" command
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 5c0ec91eb9423e6bae1b60e26b430dc96cada236 Author: Duncan <duncan(a)torproject.org> Date: Thu Feb 18 21:35:14 2021 +0000 Fix "restart tor" command --- .../images/outreach/print/onion-guide-fanzine.pdf | Bin 343863 -> 346542 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/assets/static/images/outreach/print/onion-guide-fanzine.pdf b/assets/static/images/outreach/print/onion-guide-fanzine.pdf index 4416930..dd446d9 100644 Binary files a/assets/static/images/outreach/print/onion-guide-fanzine.pdf and b/assets/static/images/outreach/print/onion-guide-fanzine.pdf differ

1 0

[community/staging] replace \ with \ U to prevent escaping errors
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 7e6ce5302f1b6b451397a31b6bdcf174d2f412be Author: emma peel <emma.peel(a)riseup.net> Date: Tue Mar 2 15:51:20 2021 +0100 replace \ with \U to prevent escaping errors --- .../technical-setup/bridge/windows/contents.lr | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/windows/contents.lr b/content/relay-operations/technical-setup/bridge/windows/contents.lr index 7bf3ddc..5ce0b6c 100644 --- a/content/relay-operations/technical-setup/bridge/windows/contents.lr +++ b/content/relay-operations/technical-setup/bridge/windows/contents.lr @@ -22,24 +22,24 @@ You will need to show hidden items and file name extensions. In your Explorer wi ### 2. Build files and relocate -Open up the Tor folder on your desktop. Double click `tor.exe`. Once the command prompt reads: `[notice] Bootstrapped 100% (done): Done`, close the window. This creates the folder `C:\Users\<user>\AppData\Roaming\tor\` (where `<user>` is your user name). +Open up the Tor folder on your desktop. Double click `tor.exe`. Once the command prompt reads: `[notice] Bootstrapped 100% (done): Done`, close the window. This creates the folder `C:\Users\<user>\AppData\Roaming\tor\` (where `<user>` is your user name). -From the Tor folder on your desktop, select all `.dll`'s and `.exe`'s and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. +From the Tor folder on your desktop, select all `.dll`'s and `.exe`'s and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. -Open up the Data folder on your desktop. Inside that Tor folder, select both `geoip` and `geoip6` and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. +Open up the Data folder on your desktop. Inside that Tor folder, select both `geoip` and `geoip6` and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. -Navigate to `C:\Users\<user>\Desktop\Tor Browser\Browser\TorBrowser\Tor\PluggableTransports`. Select `obfs4proxy.exe` and cut/paste it into the `C:\Users\<user>\AppData\Roaming\tor\` folder. +Navigate to `C:\Users\<user>\Desktop\Tor Browser\Browser\TorBrowser\Tor\PluggableTransports`. Select `obfs4proxy.exe` and cut/paste it into the `C:\Users\<user>\AppData\Roaming\tor\` folder. ### 3. Create and edit your Tor config file -In the `C:\Users\<user>\AppData\Roaming\tor\` folder, right-click on white space and select `New > Text Document`. Name the file `torrc`; there is no extension. +In the `C:\Users\<user>\AppData\Roaming\tor\` folder, right-click on white space and select `New > Text Document`. Name the file `torrc`; there is no extension. Double-click on the `torrc` file. When prompted *How do you want to open this file?*, select `Notepad`. Add the following: ``` -Log notice file C:\Users\<user>\AppData\Roaming\tor\notice.log -GeoIPFile C:\Users\<user>\AppData\Roaming\tor\geoip -GeoIPv6File C:\Users\<user>\AppData\Roaming\tor\geoip6 +Log notice file C:\Users\<user>\AppData\Roaming\tor\notice.log +GeoIPFile C:\Users\<user>\AppData\Roaming\tor\geoip +GeoIPv6File C:\Users\<user>\AppData\Roaming\tor\geoip6 BridgeRelay 1 @@ -48,7 +48,7 @@ BridgeRelay 1 # Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port. ORPort TODO1 -ServerTransportPlugin obfs4 exec C:\Users\<user>\AppData\Roaming\tor\obfs4proxy.exe +ServerTransportPlugin obfs4 exec C:\Users\<user>\AppData\Roaming\tor\obfs4proxy.exe # Replace "TODO2" with an obfs4 port of your choice. # This port must be externally reachable and must be different from the one specified for ORPort. @@ -77,11 +77,11 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, ### 4. Start tor -Open up the Command Prompt App. Change your directory with: `cd C:\Users\<user>\AppData\Roaming\tor\`. Type: `tor.exe -f torrc`. +Open up the Command Prompt App. Change your directory with: `cd C:\Users\<user>\AppData\Roaming\tor\`. Type: `tor.exe -f torrc`. ### 5. Monitor your logs -To confirm your bridge is running with no issues, you should see something like this in `C:\Users\<user>\AppData\Roaming\tor\notice.log`. +To confirm your bridge is running with no issues, you should see something like this in `C:\Users\<user>\AppData\Roaming\tor\notice.log`. ``` [notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>'

1 0

[community/staging] Update contents.lr
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 681232c6ba8cbd43e808399724e776d3ef8b6d92 Author: Llim3s <79686472+Llim3s(a)users.noreply.github.com> Date: Tue Mar 2 17:03:42 2021 +0100 Update contents.lr read some terms of service and contacted a bunch of hosters in germany and wrote down the results --- .../community-resources/good-bad-isps/contents.lr | 35 ++++++++++++++-------- 1 file changed, 23 insertions(+), 12 deletions(-) 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 f8da4ae..c6dca64 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -87,19 +87,30 @@ For network diversity and stronger anonymity, you should avoid providers and cou | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| | [Weesly](http://weesly.de) | - | Yes | Yes | Yes | Note that you should let them know about your intention when ordering a server or in advance. | 06/2013 | -| [EUServ](http://euserv.de) | - | - | Yes | No | They have a bad support, but if you know how to maintain your server, this ISP is a good choice. | - | -| [IPX-Server](https://www.ipx-server.de/) | - | Yes | Yes | - | - | - | -| [Keyweb](https://www.keyweb.de/) | - | - | No | No | "Unfortunately this is not possible with us." | 2020 | -| [Afterburst](http://afterburst.com) | - | - | Yes | No | - | - | +| [EUServ](http://euserv.de) | AS35366 | Yes | Yes | Yes | "Relays only allowed on dedicated Servers Prime64 and Pro64, Exit nodes only allowed on Prime64 and Pro64 with Pro-Option, own subnet, RIPE entry along with publicly visible abuse and police contact." | 03/2021 | +| [IPX-Server](https://www.ipx-server.de) | - | Yes | Yes | - | - | - | +| [Keyweb](https://www.keyweb.de) | AS31103 | Yes | Yes | Yes | "Everything that is in accordance with current jurisprudence is permitted on our servers." | 03/2021 | +| [Afterburst](http://afterburst.com) | AS29761, AS8100 | - | Yes | No | - | - | | [myLoc Managed IT](https://myloc.de) | AS31010, AS24961 | Yes | Yes | No | - | 2018-10-25 | -| [linevast](https://www.linevast.de/) | - | Yes | Yes | Yes | Only allowed on dedicated servers | 13/11/2015 | -| [Server4You](https://www.server4you.de/)| - | Yes | Yes | No | Part of [Intergenia AG](http://www.intergenia.de/)), I've asked Server4You support and they state servers with complaints about Tor will be canceled immediately (see the quote in the "Bad Experience" section) | - | -| [Hetzner](http://hetzner.de/) | - | - | Yes | No | Offers good dedicated root servers for a good price. | - | -| [Contabo](https://contabo.de) | - | Yes | Yes | Yes | Has no restriction for relays or exit nodes. However, possible abuse complaints will be forwarded to the owner and need to be addressed. | 2018/06 | -| [Strato](https://strato.de) | - | - | Yes | No | Exit-Nodes are prohibited by their general terms and conditions | - | -| [PraHost](https://www.prahost.com/) | - | - | Yes | Yes | Stated in November 2014 that they allow exit nodes if abuse complaints are handled. Suspends the server if no "valid" action (read: blocking) is taken within 24 hours of an abuse ticket. Their ticket system does not reliably handle email replies, use the web interface instead. | 2017-10-31 | -| [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server/) | - | - | Yes | No | - | - | -| [NetCologne](https://www.netcologne.de/) | - | - | Yes | Yes | - | - | +| [linevast](https://www.linevast.de) | AS201206 | No | No | No | | 03/2021 | +| [Server4You](https://www.server4you.de)| AS131914 | No | No | No | - | 03/2021 | +| [Hetzner](http://hetzner.de) | AS24940 | Yes | Yes | Yes | Offers good dedicated root servers for a good price. "It is not a Problem, however, abuse reports can lead to a server lock" | 03/2021 | +| [Contabo](https://contabo.de) | AS51167 | No | No | No | TOR prohibited due to terms of service | 03/2021 | +| [Strato](https://strato.de) | AS6724 | No | No | No | - | 03/2021 | +| [PraHost](https://www.prahost.com) | - | Yes | Yes | Yes | "If there is any abuse notice received, you need to solve it in given time, else your IP will be blocked until you take any action" | 03/2021 | +| [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server) | AS34011 | Yes | Yes | Yes | Only allowed on jiffybox | 03/2021 | +| [NetCologne](https://www.netcologne.de) | - | - | Yes | Yes | - | - | +| [Signaltransmitter](https://signaltransmitter.de) | AS24961 | Yes | Yes | Yes | "In principle, we do not limit our services apart from mining bitcoins" | 03/2021 | +| [Netcup](https://www.netcup.de) | AS197540 | Yes | Yes | Yes | TOR allowed on VPS and rootservers | 03/2021 | +| [Onyxhosting](https://onyxhosting.de) | - | No | No | No | - | 03/2021 | +| [IP-Projects](https://www.ip-projects.de) | AS48314 | No | No | No | - | 03/2021 | +| [Lansol](https://www.lansol.de) | - | No | No | No | - | 03/2021 | +| [delta.networks](https://www.delta-networks.de) | AS9937 | No | No | No | - | 03/2021 | +| [VPS2Day](https://www.vps2day.com) | AS58329 | Yes | Yes | No | Exit nodes prohibited due to terms of service | 03/2021 | +| [Serverprofis](https://www.serverprofis.de) | AS5539 | No | No | No | - | 03/2021 | +| [manitu](https://www.manitu.de) | AS34240 | No | No | No | "I´m sorry - even if the network has great added value for specific purposes, we have decided to prohibit TOR services on our network" | 03/2021 | +| [active-servers](https://www.active-servers.com) | AS197071 | Yes | Yes | Yes | "Usually this leads to abuse mails, which only cause trouble – but basically we have nothing against it" | 03/2021 | +| [UltraVPS](https://www.ultravps.eu) | - | No | No | No | "We are not the right host for your project" | 03/2021 | ### Hong Kong

1 0

[community/staging] better lines for l10n
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 90e75e26e5d50659e7ac868e3e18f6d1795d9d9e Author: emma peel <emma.peel(a)riseup.net> Date: Tue Mar 2 10:22:00 2021 +0100 better lines for l10n --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 6 ++---- .../technical-setup/bridge/debian-ubuntu/contents.lr | 6 ++---- .../technical-setup/bridge/dragonflybsd/contents.lr | 3 ++- content/relay-operations/technical-setup/bridge/fedora/contents.lr | 6 ++---- content/relay-operations/technical-setup/bridge/openbsd/contents.lr | 6 ++---- 5 files changed, 10 insertions(+), 17 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index aa356c0..7701282 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -125,10 +125,8 @@ To confirm your bridge is running with no issues, you should see something like ### 6. Final notes -If you are having trouble setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/getting-help/). If -your bridge is now running, check out the [post-install -notes](https://community.torproject.org/relay/setup/bridge/post-install/). +If you are having trouble setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). +If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). --- html: two-columns-page.html diff --git a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr index c820d2c..8dfc9e7 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -82,10 +82,8 @@ To confirm your bridge is running with no issues, you should see something like ### 6. Final notes -If you are having trouble setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/getting-help/). If -your bridge is now running, check out the [post-install -notes](https://community.torproject.org/relay/setup/bridge/post-install/). +If you are having trouble setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). +If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). --- key: 1 diff --git a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr index 22d58ad..8a0c15e 100644 --- a/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/dragonflybsd/contents.lr @@ -135,7 +135,8 @@ tail /var/log/tor/notices.log ### 6. Final Notes -If you are having troubles setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). +If you are having troubles setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). +If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). --- subtitle: How to deploy an obfs4 bridge on DragonflyBSD diff --git a/content/relay-operations/technical-setup/bridge/fedora/contents.lr b/content/relay-operations/technical-setup/bridge/fedora/contents.lr index 97b9382..6708a92 100644 --- a/content/relay-operations/technical-setup/bridge/fedora/contents.lr +++ b/content/relay-operations/technical-setup/bridge/fedora/contents.lr @@ -97,10 +97,8 @@ To confirm your bridge is running with no issues, you should see something like ### 6. Final notes -If you are having trouble setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/getting-help/). If -your bridge is now running, check out the [post-install -notes](https://community.torproject.org/relay/setup/bridge/post-install/). +If you are having trouble setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). +If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). --- html: two-columns-page.html diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index e5aed5f..d5ef072 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -87,10 +87,8 @@ To confirm your bridge is running with no issues, you should see something like ### 6. Final notes -If you are having trouble setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/getting-help/). If -your bridge is now running, check out the [post-install -notes](https://community.torproject.org/relay/setup/bridge/post-install/). +If you are having trouble setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). +If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). --- subtitle: How to deploy an obfs4 bridge on OpenBSD

1 0