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

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

24 Mar '21

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

1 0

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

24 Mar '21

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

1 0

[translation/tbmanual-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot
by translation＠torproject.org 24 Mar '21

24 Mar '21

commit 0d69b8b4d435466e0fce8ee0c36ab71266bb1071 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Mar 24 12:46:55 2021 +0000 https://gitweb.torproject.org/translation.git/commit/?h=tbmanual-contentspot --- contents+es.po | 35 ++++++++++++++++++++++++++++++++++- 1 file changed, 34 insertions(+), 1 deletion(-) diff --git a/contents+es.po b/contents+es.po index 009c61e864..5298916868 100644 --- a/contents+es.po +++ b/contents+es.po @@ -1772,6 +1772,9 @@ msgid "" "If you can't connect to an onion site, Tor Browser will provide a specific " "error message informing why the website is unavailable." msgstr "" +"Si no puedes conectar a un sitio cebolla, el Navegador Tor proveerá un " +"mensaje específico de error informando por qué el sitio web no está " +"disponible." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1779,12 +1782,16 @@ msgid "" "Errors can happen in different layers: client errors, network errors or " "service errors." msgstr "" +"Los errores pueden suceder en diferentes capas: errores de cliente, de red o" +" de servicio." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) msgid "" "Some of these errors can be fixed by following the Troubleshooting section." msgstr "" +"Algunos de estos errors pueden ser arreglados siguiendo la sección Solución " +"de Problemas." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1792,11 +1799,13 @@ msgid "" "The table below shows all the possible errors and which action you should " "take to solve the issue." msgstr "" +"La tabla de abajo muestra todos los posibles errores y qué acción deberías " +"tomar para resolver la cuestión." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) msgid "| **Code** | **Error Title** | **Short Description** |" -msgstr "" +msgstr "| **Código** | **Título del Error** | **Descripción Corta** |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1809,6 +1818,9 @@ msgid "" "| XF0 | Onion site Not Found | The most likely cause is that the onion site " "is offline or disabled. Contact the onion site administrator. |" msgstr "" +"| XF0 | Sitio Cebolla No Encontrado | La causa más probable es que el sitio " +"cebolla esté fuera de línea o deshabilitado. Contacta al administrador del " +"sitio cebolla. |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1816,6 +1828,8 @@ msgid "" "| XF1 | Onion site Cannot Be Reached | The onion site is unreachable due to " "an internal error. |" msgstr "" +"| XF1 | El Sitio Cebolla No Puede Ser Alcanzado | El sitio cebolla es " +"inalcanzable debido a un error interno. |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1823,6 +1837,9 @@ msgid "" "| XF2 | Onion site Has Disconnected | The most likely cause is that the " "onion site is offline or disabled. Contact the onion site administrator. |" msgstr "" +"| XF2 | El Sitio Cebolla Se Ha Desconectado | La causa más probable es que " +"el sitio cebolla esté fuera de línea o deshabilitado. Contacta al " +"administrador del sitio cebolla. |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1830,6 +1847,8 @@ msgid "" "| XF3 | Unable to Connect to Onion site | The onion site is busy or the Tor " "network is overloaded. Try again later. |" msgstr "" +"| XF3 | Incapaz De Conectarse Al Sitio Cebolla | El sitio cebolla está " +"ocupado o la red Tor está sobrecargada. Inténtalo más tarde. |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1837,6 +1856,8 @@ msgid "" "| XF4 | Onion site Requires Authentication | Access to the onion site " "requires a key but none was provided. |" msgstr "" +"| XF4 | El Sitio Cebolla Requiere Autenticación | El acceso al sitio cebolla" +" requiere una clave, pero ninguna fue provista. |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1844,6 +1865,9 @@ msgid "" "| XF5 | Onion site Authentication Failed | The provided key is incorrect or " "has been revoked. Contact the onion site administrator. |" msgstr "" +"| XF5 | Falló La Autenticación Del Sitio Cebolla | La clave proporcionada es" +" incorrecta o ha sido revocada. Contacta al administrador del sitio cebolla." +" |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1851,6 +1875,9 @@ msgid "" "| XF6 | Invalid Onion site Address | The provided onion site address is " "invalid. Please check that you entered it correctly. |" msgstr "" +"| XF6 | Dirección Del Sitio Cebolla Inválida | La dirección provista para el" +" sitio cebolla no es válida. Por favor, comprueba que la hayas introducido " +"correctamente. |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1858,6 +1885,8 @@ msgid "" "| XF7 | Onion site Circuit Creation Timed Out | Failed to connect to the " "onion site, possibly due to a poor network connection. |" msgstr "" +"| XF7 | Demora Excesiva En La Creación Del Circuito Para El Sitio Cebolla | " +"Fallo al conectar al sitio cebolla, quizá por una mala conexión de red. |" #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body) @@ -1882,6 +1911,10 @@ msgid "" "address, please try again later. There may be a temporary connection issue, " "or the site operators may have allowed it to go offline without warning." msgstr "" +"Si todavía no puedes conectar al servicio cebolla luego de verificar la " +"dirección, por favor, inténtalo de nuevo más tarde. Puede haber un problema " +"temporario de conexión, o los operadores del sitio pueden haberle permitido " +"salir de línea sin advertencia." #: https//tb-manual.torproject.org/onion-services/ #: (content/onion-services/contents+en.lrtopic.body)

1 0

[community/staging] Remove old projects so they don't appear in sidenav
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 0e16d7dcba183cd0a3d3c04cc1b66094a28be434 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Mar 9 09:26:20 2021 +0100 Remove old projects so they don't appear in sidenav --- content/gsoc/{ => archive}/cloudflare-captcha-monitoring/contents.lr | 0 content/gsoc/{ => archive}/gettor-distribution/contents.lr | 0 content/gsoc/{ => archive}/onion-toolbox/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-findings/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-testing/contents.lr | 0 content/gsoc/{ => archive}/ooni-probe-desktop-custom-urls/contents.lr | 0 content/gsoc/{ => archive}/privacy-aware-geo-lookup/contents.lr | 0 content/gsoc/{ => archive}/privacy-friendly-web/contents.lr | 0 content/gsoc/{ => archive}/salmon-bridge-distribution/contents.lr | 0 content/gsoc/{ => archive}/snowflake-android-proxy/contents.lr | 0 content/gsoc/{ => archive}/tor-keygen/contents.lr | 0 content/gsoc/{ => archive}/tor-relay-ipv6-support/contents.lr | 0 12 files changed, 0 insertions(+), 0 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/archive/cloudflare-captcha-monitoring/contents.lr similarity index 100% rename from content/gsoc/cloudflare-captcha-monitoring/contents.lr rename to content/gsoc/archive/cloudflare-captcha-monitoring/contents.lr diff --git a/content/gsoc/gettor-distribution/contents.lr b/content/gsoc/archive/gettor-distribution/contents.lr similarity index 100% rename from content/gsoc/gettor-distribution/contents.lr rename to content/gsoc/archive/gettor-distribution/contents.lr diff --git a/content/gsoc/onion-toolbox/contents.lr b/content/gsoc/archive/onion-toolbox/contents.lr similarity index 100% rename from content/gsoc/onion-toolbox/contents.lr rename to content/gsoc/archive/onion-toolbox/contents.lr diff --git a/content/gsoc/ooni-explorer-findings/contents.lr b/content/gsoc/archive/ooni-explorer-findings/contents.lr similarity index 100% rename from content/gsoc/ooni-explorer-findings/contents.lr rename to content/gsoc/archive/ooni-explorer-findings/contents.lr diff --git a/content/gsoc/ooni-explorer-testing/contents.lr b/content/gsoc/archive/ooni-explorer-testing/contents.lr similarity index 100% rename from content/gsoc/ooni-explorer-testing/contents.lr rename to content/gsoc/archive/ooni-explorer-testing/contents.lr diff --git a/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr b/content/gsoc/archive/ooni-probe-desktop-custom-urls/contents.lr similarity index 100% rename from content/gsoc/ooni-probe-desktop-custom-urls/contents.lr rename to content/gsoc/archive/ooni-probe-desktop-custom-urls/contents.lr diff --git a/content/gsoc/privacy-aware-geo-lookup/contents.lr b/content/gsoc/archive/privacy-aware-geo-lookup/contents.lr similarity index 100% rename from content/gsoc/privacy-aware-geo-lookup/contents.lr rename to content/gsoc/archive/privacy-aware-geo-lookup/contents.lr diff --git a/content/gsoc/privacy-friendly-web/contents.lr b/content/gsoc/archive/privacy-friendly-web/contents.lr similarity index 100% rename from content/gsoc/privacy-friendly-web/contents.lr rename to content/gsoc/archive/privacy-friendly-web/contents.lr diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/archive/salmon-bridge-distribution/contents.lr similarity index 100% rename from content/gsoc/salmon-bridge-distribution/contents.lr rename to content/gsoc/archive/salmon-bridge-distribution/contents.lr diff --git a/content/gsoc/snowflake-android-proxy/contents.lr b/content/gsoc/archive/snowflake-android-proxy/contents.lr similarity index 100% rename from content/gsoc/snowflake-android-proxy/contents.lr rename to content/gsoc/archive/snowflake-android-proxy/contents.lr diff --git a/content/gsoc/tor-keygen/contents.lr b/content/gsoc/archive/tor-keygen/contents.lr similarity index 100% rename from content/gsoc/tor-keygen/contents.lr rename to content/gsoc/archive/tor-keygen/contents.lr diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/archive/tor-relay-ipv6-support/contents.lr similarity index 100% rename from content/gsoc/tor-relay-ipv6-support/contents.lr rename to content/gsoc/archive/tor-relay-ipv6-support/contents.lr

1 0

[community/staging] Add GSoC 2021 OONI Projects
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 9a05fe9d348c40e779dae17c6cd65df7dfa4e0f2 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Mar 9 10:11:35 2021 +0100 Add GSoC 2021 OONI Projects --- .../gsoc/ooni-explorer-code-quality/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-geoip-accuracy/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-probe-testing/contents.lr | 67 ++++++++++++++++++++++ content/gsoc/ooni-roaming-test/contents.lr | 64 +++++++++++++++++++++ 4 files changed, 253 insertions(+) diff --git a/content/gsoc/ooni-explorer-code-quality/contents.lr b/content/gsoc/ooni-explorer-code-quality/contents.lr new file mode 100644 index 0000000..a24f332 --- /dev/null +++ b/content/gsoc/ooni-explorer-code-quality/contents.lr @@ -0,0 +1,61 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 6 +--- +languages: +Javascript +ReactJS +Typescript +--- +org: OONI +--- +mentors: +Sarath +--- +difficulty: Advanced +--- +title: OONI: Improve OONI Explorer code quality +--- +subtitle: + +OONI Explorer is an open data resource on internet censorship around the world. As part of this project you would be working on helping to port OONI Explorer code to Typescript. +--- +body: + +# Background + +The Open Observatory of Network Interference (OONI) is a free software project which aims to empower decentralized efforts in increasing transparency of internet censorship around the world. + +OONI Explorer is an open data resource on internet censorship around the world. + +# Proposal + +Typescript has been adopted widely as a way to write more reliable JS applications and now has a well supported toolchain and an active and growing community. We could benefit from porting parts or all of the OONI Explorer code to Typescript especially to be able to handle unpredictable data in API responses. Next.js, the underlying react framework the project is built upon, also has first-class support for Typescript. The project involves: + +1. coming up with a strategy to incrementally port the codebase +1. ensuring integration with other projects in `ooni-components` +1. rewrite code +1. writing unit tests for critical react components in the projects +1. improve build process to leverage typescript features + +- **Prerequisites:** Experience in Typescript, nice to have knowledge of Next.js + +# Resources + +- OONI Explorer repo on github: https://github.com/ooni/explorer +- OONI Explorer issues github: https://github.com/ooni/explorer/issues +- https://github.com/ooni/design-system +- https://nextjs.org/docs/basic-features/typescript +- https://www.typescriptlang.org/ \ No newline at end of file diff --git a/content/gsoc/ooni-geoip-accuracy/contents.lr b/content/gsoc/ooni-geoip-accuracy/contents.lr new file mode 100644 index 0000000..1d7950d --- /dev/null +++ b/content/gsoc/ooni-geoip-accuracy/contents.lr @@ -0,0 +1,61 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 5 +--- +languages: +Java +Python +--- +org: OONI +--- +mentors: +Arturo +Federico +--- +difficulty: Medium +--- +title: OONI: Measure the accuracy of OONI GeoIP lookup +--- +subtitle: + +OONI Probe is a free software project that aims to uncover internet censorship around the world. As part of this project you would be working on developing a strategy and tooling for assessing the accuracy of our GeoIP databases. +--- +body: + +# Background + +The Open Observatory of Network Interference (OONI) is a free software project which aims to empower decentralized efforts in increasing transparency of internet censorship around the world. + +We develop free and open source software, called OONI Probe, that users can run to measure: + +- Blocking of websites; +- Blocking of instant messaging apps (WhatsApp, Facebook Messenger and Telegram); +- Blocking of censorship circumvention tools (such as Tor); +- Presence of systems (middleboxes) in your network that might be responsible for censorship and/or surveillance; +- Speed and performance of your network. + +By running OONI Probe, users can collect data that can potentially serve as evidence of internet censorship since it shows how, when, where, and by whom it is implemented. + +# Proposal + +When attributing OONI Probe measurements to specific countries we rely on GeoIP databases (https://github.com/ooni/asn-db-generator) These database at times will attribute measurements to the wrong country. We don't currently have a good way of measuring how reliable this approach to geolocation is. +This project is about developing a strategy and tooling for assessing the accuracy of our GeoIP databases by comparing the GeoIP resolution to other location data from the probe, mostly cell tower information and GPS, while respecting user's privacy. + +- **Prerequisites:** Knowledge of Android development and ideally backend development in python + +# Resources + +- OONI Probe Engine repo on github: https://github.com/ooni/probe-engine +- Link to issue: https://github.com/ooni/probe-engine/issues/249 diff --git a/content/gsoc/ooni-probe-testing/contents.lr b/content/gsoc/ooni-probe-testing/contents.lr new file mode 100644 index 0000000..0a8d752 --- /dev/null +++ b/content/gsoc/ooni-probe-testing/contents.lr @@ -0,0 +1,67 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 7 +--- +languages: +Javascript +ReactJS +--- +org: OONI +--- +mentors: +Sarath +--- +difficulty: Medium +--- +title: OONI: Integration and unit testing of OONI Probe Desktop apps +--- +subtitle: + +OONI Probe is a free software project that aims to uncover internet censorship around the world. As part of this project you would be working on integration and unit testing of OONI Probe Desktop apps. + +--- +body: + +# Background + +The Open Observatory of Network Interference (OONI) is a free software project which aims to empower decentralized efforts in increasing transparency of internet censorship around the world. + +We develop free and open source software, called OONI Probe, that users can run to measure: + +- Blocking of websites; +- Blocking of instant messaging apps (WhatsApp, Facebook Messenger and Telegram); +- Blocking of censorship circumvention tools (such as Tor); +- Presence of systems (middleboxes) in your network that might be responsible for censorship and/or surveillance; +- Speed and performance of your network. + +By running OONI Probe, users can collect data that can potentially serve as evidence of internet censorship since it shows how, when, where, and by whom it is implemented. + +# Proposal + +This project aims to: + +1. add support for automated testing of the desktop app to emulate the user stories end-to-end +1. add support for unit testing react components and javascript code running in electron's `main` process. + +It may be necessary to refactor parts of the codebase and upgrade dependencies to improve testability. The student is encouraged to research existing testing tools and propose solutions that can help complete the project. + +*Prerequisites:* None + +# Resources + +- https://github.com/ooni/probe-desktop/ +- http://electronjs.org/spectron +- https://docs.cypress.io/guides/component-testing/introduction.html +- https://testing-library.com/docs/react-testing-library/intro \ No newline at end of file diff --git a/content/gsoc/ooni-roaming-test/contents.lr b/content/gsoc/ooni-roaming-test/contents.lr new file mode 100644 index 0000000..fb0e4ac --- /dev/null +++ b/content/gsoc/ooni-roaming-test/contents.lr @@ -0,0 +1,64 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 4 +--- +languages: +Python +--- +org: OONI +--- +mentors: +Federico +--- +difficulty: Medium/Advanced +--- +title: OONI: Implement roaming test helpers +--- +subtitle: + +OONI Probe is a free software project that aims to uncover internet censorship around the world. As part of this project you would be working on improving censorship detection while making the OONI infrastructure more resilient. +--- +body: + +# Background + +The Open Observatory of Network Interference (OONI) is a free software project which aims to empower decentralized efforts in increasing transparency of internet censorship around the world. + +We develop free and open source software, called OONI Probe, that users can run to measure: + +- Blocking of websites; +- Blocking of instant messaging apps (WhatsApp, Facebook Messenger and Telegram); +- Blocking of censorship circumvention tools (such as Tor); +- Presence of systems (middleboxes) in your network that might be responsible for censorship and/or surveillance; +- Speed and performance of your network. + +By running OONI Probe, users can collect data that can potentially serve as evidence of internet censorship since it shows how, when, where, and by whom it is implemented. + +# Proposal + +Test helpers are endpoints used by the OONI Probes to detect censorship. The main goal of the project is to improve censorship detection while making the OONI infrastructure more resilient. The main activities are: + +1. Deploy and integrate new test helpers based on the probe codebase. +1. Automate deployment and rotation of test helpers on various public clouds. +1. Implement forwarding methods to use the test helpers as proxies for the collector API. +1. Safely serve metadata about the test collectors through the API. + +- **Prerequisites:** Understanding of Networking, Security, OS, basics of cloud services + +# Resources + + + +

1 0

[community/staging] Merge branch 'gsoc-captcha'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 27dcbdab8b10af5e978b9fc7f9de51c34fe17dad Merge: 8c859d5 d64491d Author: gus <gus(a)torproject.org> Date: Mon Mar 8 12:50:59 2021 -0300 Merge branch 'gsoc-captcha' content/gsoc/alexa-captcha-monitoring/contents.lr | 83 +++++++++++++++++++++++ 1 file changed, 83 insertions(+)

1 0

[community/staging] Merge branch 'gsoc-onionbalance'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 37c49862c5258b4b7d1e539e3572ede1426897b2 Merge: 27dcbda db3e235 Author: gus <gus(a)torproject.org> Date: Mon Mar 8 12:51:15 2021 -0300 Merge branch 'gsoc-onionbalance' content/gsoc/onion-balance-v3/contents.lr | 57 +++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+)

1 0

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

24 Mar '21

commit 74b84108b2a86e89bb72c511bb734ced856fe00c Author: hiro <hiro(a)torproject.org> Date: Mon Mar 15 18:12:44 2021 +0100 Edit template and slides --- assets/static/images/onion-white.png | Bin 0 -> 41138 bytes assets/static/images/onion.jpg | Bin 0 -> 3911 bytes assets/static/images/onion.png | Bin 0 -> 41071 bytes assets/static/revealjs/dist/theme/tor.css | 37 +++++- .../training/resources/tor-training/contents.lr | 126 +++++++++++++++++---- flowblocks/slide.ini | 9 ++ templates/blocks/slide.html | 8 ++ templates/slideshow.html | 7 +- 8 files changed, 160 insertions(+), 27 deletions(-) diff --git a/assets/static/images/onion-white.png b/assets/static/images/onion-white.png new file mode 100644 index 0000000..f8daf6a Binary files /dev/null and b/assets/static/images/onion-white.png differ diff --git a/assets/static/images/onion.jpg b/assets/static/images/onion.jpg new file mode 100644 index 0000000..d728622 Binary files /dev/null and b/assets/static/images/onion.jpg differ diff --git a/assets/static/images/onion.png b/assets/static/images/onion.png new file mode 100644 index 0000000..ce6dcdf Binary files /dev/null and b/assets/static/images/onion.png differ diff --git a/assets/static/revealjs/dist/theme/tor.css b/assets/static/revealjs/dist/theme/tor.css index 31b0054..2c55510 100644 --- a/assets/static/revealjs/dist/theme/tor.css +++ b/assets/static/revealjs/dist/theme/tor.css @@ -20,7 +20,7 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba --block-margin: 20px; --heading-margin: 0 0 20px 0; --heading-font: Source Sans Pro, Helvetica, sans-serif; - --heading-color: #59316B; + --heading-color: #683086; --heading-line-height: 1.2; --heading-letter-spacing: normal; --heading-text-transform: uppercase; @@ -32,7 +32,7 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba --heading3-size: 1.3em; --heading4-size: 1em; --code-font: monospace; - --link-color: #59316B; + --link-color: #683086; --link-color-hover: #9400ff; --selection-background-color: #98bdef; --selection-color: #fff; } @@ -72,7 +72,7 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba .reveal h5, .reveal h6 { margin: 0 0 20px 0; - color: #59316B; + color: #683086; font-family: "Source Sans Pro", Helvetica, sans-serif; font-weight: 600; line-height: 1.2; @@ -244,6 +244,10 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba .reveal img { margin: 20px 0; } +.reveal hr { + border: 5px solid #fff; +} + /********************************************* * LINKS *********************************************/ @@ -275,6 +279,10 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba border-color: #2a76dd; box-shadow: 0 0 20px rgba(0, 0, 0, 0.55); } + +.title div { + background-position: 85% 85% !important; +} /********************************************* * NAVIGATION CONTROLS *********************************************/ @@ -294,3 +302,26 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba @media print { .backgrounds { background-color: #fff; } } + +/********************************************* + * FOOTER + *********************************************/ + +.footer { + background-color: #683086; +} + +/********************************************* + * OVERRIDES + *********************************************/ + +.slides { + text-align: left !important; +} +.title { + text-align: center; +} + +hr.dark { + border: 5px solid #683086; +} diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index c37e94b..16254df 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -1,32 +1,21 @@ _model: slideshow --- -title: Tor Presentation +title: The Tor Network --- _template: slideshow.html --- -subtitle: Teach your community about using Tor ---- -author: Community Team ---- background: white --- -image: /static/images/onion-bg.png +image: /static/images/onion.png --- slides: -#### slide #### -title: Hello Slideshow ----- -description: Test slides ----- -background: white - #### slide #### title: Topics ---- description: -- What’s Tor? +- What' s Tor? - Types of relays - Technical setup - More about relays @@ -43,7 +32,7 @@ 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 +- It' s Tor, not TOR ---- background: white @@ -71,13 +60,108 @@ By running a Tor relay you can help make the Tor network: background: white #### slide #### -title: Why run a Tor relay? +title: Types of Relays +---- +layout: title +---- +background-image: /static/images/onion-white.png + +#### slide #### +title: Guard/middle (aka non-exit) 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) +- 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 diff --git a/flowblocks/slide.ini b/flowblocks/slide.ini index 97b1b6b..23cf3fb 100644 --- a/flowblocks/slide.ini +++ b/flowblocks/slide.ini @@ -19,3 +19,12 @@ source = record.attachments.images [fields.background] label = Background color type = string + +[fields.layout] +label = Slide layout +type = string + +[fields.background-image] +label = Background image +type = string +translate = False diff --git a/templates/blocks/slide.html b/templates/blocks/slide.html index 5f96574..e0421ea 100644 --- a/templates/blocks/slide.html +++ b/templates/blocks/slide.html @@ -1,5 +1,13 @@ +{% if this.layout == "title" %} +<section class="title" data-background-color="white" data-background-image="{{ this.image|asseturl }}" data-background-position="right bottom" data-background-size="3em"> + <h3>{{ this.title }}</h3> + <hr class="dark" /> + <h4>{{ this.subtitle }}</h4> +</section> +{% else %} <section data-background-color="{{ this.background }}"> <h2>{{ this.title }}</h2> {{ this.description }} </section> +{% endif %} diff --git a/templates/slideshow.html b/templates/slideshow.html index 260c123..f1d6065 100644 --- a/templates/slideshow.html +++ b/templates/slideshow.html @@ -17,9 +17,10 @@ <div class="reveal">  <div class="slides"> - <section data-background-color="{{ this.background }}" data-background-image="{{ this.image|asseturl }}" data-background-position="bottom right" data-background-size="3em"> - <h1>{{ this.title }}</h1> - <h2>{{ this.subtitle }}</h2> + <section class="title" data-background-color="#683086" data-background-image="{{ this.image|asseturl }}" data-background-position="right bottom" data-background-size="3em"> + <h3>{{ this.title }}</h3> + <hr /> + <h4>{{ this.subtitle }}</h4> <p>{{ this.author }}</p> </section>

1 0

[community/staging] Merge branch 'gsoc-ooni-projects'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit a038308793435d7239c2358ff69c8a963d445af5 Merge: 91767c7 9a05fe9 Author: gus <gus(a)torproject.org> Date: Tue Mar 9 15:00:07 2021 -0300 Merge branch 'gsoc-ooni-projects' .../gsoc/ooni-explorer-code-quality/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-geoip-accuracy/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-probe-testing/contents.lr | 67 ++++++++++++++++++++++ content/gsoc/ooni-roaming-test/contents.lr | 64 +++++++++++++++++++++ 4 files changed, 253 insertions(+)

1 0

[community/staging] Merge branch 'gsoc-archive'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 91767c79cd2671b5f11df5f7c2b6e793915f395a Merge: 37c4986 0e16d7d Author: gus <gus(a)torproject.org> Date: Tue Mar 9 14:59:44 2021 -0300 Merge branch 'gsoc-archive' content/gsoc/{ => archive}/cloudflare-captcha-monitoring/contents.lr | 0 content/gsoc/{ => archive}/gettor-distribution/contents.lr | 0 content/gsoc/{ => archive}/onion-toolbox/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-findings/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-testing/contents.lr | 0 content/gsoc/{ => archive}/ooni-probe-desktop-custom-urls/contents.lr | 0 content/gsoc/{ => archive}/privacy-aware-geo-lookup/contents.lr | 0 content/gsoc/{ => archive}/privacy-friendly-web/contents.lr | 0 content/gsoc/{ => archive}/salmon-bridge-distribution/contents.lr | 0 content/gsoc/{ => archive}/snowflake-android-proxy/contents.lr | 0 content/gsoc/{ => archive}/tor-keygen/contents.lr | 0 content/gsoc/{ => archive}/tor-relay-ipv6-support/contents.lr | 0 12 files changed, 0 insertions(+), 0 deletions(-)

1 0