tor-commits March 2021

tor-commits@lists.torproject.org

17 participants
2169 discussions

[community/slideshow] 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/slideshow] 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/slideshow] 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/slideshow] 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/slideshow] 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/slideshow] 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/slideshow] Update slideshow template with ordering for localization
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 389e316cd596d3174e2cffc0d99984822cd257c1 Author: hiro <hiro(a)torproject.org> Date: Sun Mar 21 19:52:13 2021 +0100 Update slideshow template with ordering for localization --- assets/static/revealjs/dist/theme/tor.css | 21 ++++++++++++++++++++ templates/slideshow.html | 32 ++++++++++++++++--------------- 2 files changed, 38 insertions(+), 15 deletions(-) diff --git a/assets/static/revealjs/dist/theme/tor.css b/assets/static/revealjs/dist/theme/tor.css index 0ff2e67..7dc1a42 100644 --- a/assets/static/revealjs/dist/theme/tor.css +++ b/assets/static/revealjs/dist/theme/tor.css @@ -313,6 +313,19 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba .footer { background-color: #683086; + min-height: 10%; +} + +.footer img { + position:relative; + min-height: 1.5em; + padding: 5px; +} + +.footer a { + font-size: 1.5em !important; + padding: 5px; + top: 10px; } /********************************************* @@ -329,3 +342,11 @@ section.has-dark-background, section.has-dark-background h1, section.has-dark-ba hr.dark { border: 5px solid #683086; } + +.order-last { + text-align: left !important; +} + +.order-first { + text-align: right !important; +} diff --git a/templates/slideshow.html b/templates/slideshow.html index f1d6065..c6b330e 100644 --- a/templates/slideshow.html +++ b/templates/slideshow.html @@ -16,24 +16,26 @@ <body> <div class="reveal">  - <div class="slides"> - <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> + <div class="slides {{ bag('alternatives', this.alt, 'order') }}"> + <section> + <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> - {{ this.slides }} + {{ this.slides }} - <div class="footer"> - <div class="left"> - <a href="https://torproject.org">torproject.org</a> - </div> - <div class="right"> - <img src="{{ '/static/images/tor-logo/White.png'|asseturl }}"> + <div class="footer"> + <div class="left"> + <a href="https://torproject.org">torproject.org</a> + </div> + <div class="right"> + <img src="{{ '/static/images/tor-logo/White.png'|asseturl }}"> + </div> </div> - </div> + </section> </div> </div>

1 0

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

24 Mar '21

commit cfc37b8538bade8d2106272577d264b3da98da94 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 | 517 +++++++++++++++++++++ templates/blocks/slide.html | 3 +- 3 files changed, 524 insertions(+), 2 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 new file mode 100644 index 0000000..4a38efa --- /dev/null +++ b/content/training/resources/tor-training/contents.lr @@ -0,0 +1,517 @@ +_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 + + + +#### 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 + + + +#### 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. + + +#### 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) + + +#### 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 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/slideshow] Use string for localization
by hiro＠torproject.org 24 Mar '21

24 Mar '21

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

1 0

[community/slideshow] Remove projects without mentors
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 3e8e9bef671243efbc7819ce0007fa40a1856e23 Author: Pili Guerra <pili(a)piliguerra.com> Date: Thu Feb 18 17:20:34 2021 +0100 Remove projects without mentors --- content/gsoc/gettor-distribution/contents.lr | 2 +- content/gsoc/onion-toolbox/contents.lr | 2 +- content/gsoc/privacy-friendly-web/contents.lr | 2 +- content/gsoc/salmon-bridge-distribution/contents.lr | 2 +- content/gsoc/tor-keygen/contents.lr | 2 +- content/gsoc/tor-relay-ipv6-support/contents.lr | 4 +++- content/gsoc/tor-weather/contents.lr | 1 - 7 files changed, 8 insertions(+), 7 deletions(-) diff --git a/content/gsoc/gettor-distribution/contents.lr b/content/gsoc/gettor-distribution/contents.lr index 797a2ff..5639af3 100644 --- a/content/gsoc/gettor-distribution/contents.lr +++ b/content/gsoc/gettor-distribution/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/onion-toolbox/contents.lr b/content/gsoc/onion-toolbox/contents.lr index fa998f7..f1c0b0e 100644 --- a/content/gsoc/onion-toolbox/contents.lr +++ b/content/gsoc/onion-toolbox/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/privacy-friendly-web/contents.lr b/content/gsoc/privacy-friendly-web/contents.lr index 36cdd00..6d8a8e1 100644 --- a/content/gsoc/privacy-friendly-web/contents.lr +++ b/content/gsoc/privacy-friendly-web/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/salmon-bridge-distribution/contents.lr index 99a5bbf..bb33777 100644 --- a/content/gsoc/salmon-bridge-distribution/contents.lr +++ b/content/gsoc/salmon-bridge-distribution/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/tor-keygen/contents.lr b/content/gsoc/tor-keygen/contents.lr index f32192f..8b138bf 100644 --- a/content/gsoc/tor-keygen/contents.lr +++ b/content/gsoc/tor-keygen/contents.lr @@ -4,7 +4,7 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False --- section: GSoC --- diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/tor-relay-ipv6-support/contents.lr index d28a631..db89d66 100644 --- a/content/gsoc/tor-relay-ipv6-support/contents.lr +++ b/content/gsoc/tor-relay-ipv6-support/contents.lr @@ -4,7 +4,9 @@ _template: layout.html --- html: two-columns-page.html --- -active: True +active: False +--- +completed: True --- section: GSoC --- diff --git a/content/gsoc/tor-weather/contents.lr b/content/gsoc/tor-weather/contents.lr index cc6b997..b8668ad 100644 --- a/content/gsoc/tor-weather/contents.lr +++ b/content/gsoc/tor-weather/contents.lr @@ -20,7 +20,6 @@ java --- mentors: GeKo -karsten --- difficulty: medium ---

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2021