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

[community/staging] Fix broken links
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fda798cb4113eaaf9c752d1b9b606f973dcdc3a0 Author: Nicolei Ocana <nicoleiocana(a)gmail.com> Date: Thu Apr 9 19:32:27 2020 +0000 Fix broken links Merges #50 in github Closes #120 in gitlab --- .../community-resources/eff-tor-legal-faq/contents.lr | 2 +- .../community-resources/tor-abuse-templates/contents.lr | 2 +- .../community-resources/tor-exit-guidelines/contents.lr | 4 ++-- .../community-resources/tor-relay-universities/contents.lr | 2 +- content/relay-operations/relays-requirements/contents.lr | 2 +- .../technical-setup/guard/centosrhel/updates/contents.lr | 2 +- content/user-research/guidelines/contents.lr | 7 +++---- 7 files changed, 10 insertions(+), 11 deletions(-) diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr index 8e78678..b540deb 100644 --- a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr +++ b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr @@ -13,7 +13,7 @@ Therefore, please do not act on this information alone; if you have any specific Also, if you received this document from anywhere besides the EFF web site or https://community.torproject.org/relay/community-resources/eff-tor-legal-faq, it may be out of date. Follow the link to get the latest version. -Got a DMCA notice? Check out our [sample response letter](/relay/community-resources/eff-tor-legal/faq/tor-dmca-response)! +Got a DMCA notice? Check out our [sample response letter](/relay/community-resources/eff-tor-legal-faq/tor-dmca-response)! ## General Information diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index d66ede9..007e0d2 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -9,7 +9,7 @@ body: # Before You Start The best way to handle abuse complaints is to set up your exit node so that they are less likely to be sent in the first place. -Please see [Tips for Running an Exit Node with Minimal Harassment](https://blog.torproject.org/running-exit-node) and [Tor Exit Guidelines](tor-exit-guidelines) for more info, before reading this document. +Please see [Tips for Running an Exit Node with Minimal Harassment](https://blog.torproject.org/running-exit-node) and [Tor Exit Guidelines](/relay/community-resources/tor-exit-guidelines/) for more info, before reading this document. Below are a collection of letters you can use to respond to your ISP about their complaint in regards to your Tor exit server. diff --git a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr index 049da51..6552154 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -27,7 +27,7 @@ A good ISP is one that offers cheap bandwidth and is not being used by other mem Before you continue, you may ask the Tor community if your choice is a good one. We very much need diversity, and it does not help if we pool too many exits at one friendly ISP. -In any case, add the ISP to the [GoodBadISPs](good-bad-isps) page. +In any case, add the ISP to the [GoodBadISPs](/relay/community-resources/good-bad-isps/) page. To find an ISP, go through forums and sites where ISPs posts their latest deals, and contact them about Tor hosting. Once you identified your ISP, you can follow the two-step advice of TorServers.net. @@ -77,7 +77,7 @@ If you receive an abuse complaint, don't freak out! Here is some advice for you: TorServers.net is a fairly large Tor exit operator and we receive only a very small number of complaints, especially compared to the amount of traffic we push. Roughly 80% are automated reports, and the rest is usually satisfied with [our default reply](https://www.torservers.net/wiki/abuse/templates). We have not needed the input of a lawyer in many years of operation following the advice on this page. -In addition to the [templates at Torservers.net](https://www.torservers.net/wiki/abuse/templates), you can find many more templates for various scenarios on the [Tor Abuse Templates](tor-abuse-templates) . It is exceptionally rare to encounter a scenario where none of these templates apply. +In addition to the [templates at Torservers.net](https://www.torservers.net/wiki/abuse/templates), you can find many more templates for various scenarios on the [Tor Abuse Templates](/relay/community-resources/tor-abuse-templates/) . It is exceptionally rare to encounter a scenario where none of these templates apply. ### If you receive a threatening letter from a lawyer about abusive use or a DMCA complaint, also don't freak out. diff --git a/content/relay-operations/community-resources/tor-relay-universities/contents.lr b/content/relay-operations/community-resources/tor-relay-universities/contents.lr index 0b88a90..5d57cac 100644 --- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr +++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr @@ -26,7 +26,7 @@ Of course, you need to understand that without actual clear precedent (and even In any case, the key here is to become familiar with the laws and their implications and uncertainties. * Third, learn about Tor's design. -Read the [design overview](https://2019.www.torproject.org/overview.html), the [design paper](https://www.torproject.org/svn/trunk/doc/design-paper/tor-design.htm…, and the [FAQ](https://2019.www.torproject.org/docs/faq.html.en). +Read the [design overview](https://2019.www.torproject.org/overview.html), the [design paper](https://svn-archive.torproject.org/svn/projects/design-paper/tor-des…, and the [FAQ](https://2019.www.torproject.org/docs/faq.html.en). Hang out on IRC ([irc.oftc.net](https://www.oftc.net) - #tor-relays) for a while and learn more. If possible, attend a talk by one of the Tor developers. Learn about the types of people and organizations who need secure communications on the Internet. diff --git a/content/relay-operations/relays-requirements/contents.lr b/content/relay-operations/relays-requirements/contents.lr index 5ad16cc..d43f3b5 100644 --- a/content/relay-operations/relays-requirements/contents.lr +++ b/content/relay-operations/relays-requirements/contents.lr @@ -27,7 +27,7 @@ Fast exit relays (>=100 Mbit/s) usually have to handle a lot more concurrent con It is recommended that a relay have at least 16 Mbit/s (Mbps) upload bandwidth and 16 Mbit/s (Mbps) 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](relay/setup/bridge). +If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a [bridge with obfs4 support](/relay/setup/bridge/). If you do not know your bandwidth you can use http://beta.speedtest.net to measure it. # Monthly Outbound Traffic diff --git a/content/relay-operations/technical-setup/guard/centosrhel/updates/contents.lr b/content/relay-operations/technical-setup/guard/centosrhel/updates/contents.lr index 24adef4..b6e353f 100644 --- a/content/relay-operations/technical-setup/guard/centosrhel/updates/contents.lr +++ b/content/relay-operations/technical-setup/guard/centosrhel/updates/contents.lr @@ -53,7 +53,7 @@ Enable the following settings: Confirm your configuration with OK. -The official openSUSE documentation can be found [here](https://doc.opensuse.org/documentation/leap/startup/html/book.opensus…. +The official openSUSE documentation can be found [here](https://doc.opensuse.org/documentation/leap/startup/single-html/book.…. --- html: two-columns-page.html --- diff --git a/content/user-research/guidelines/contents.lr b/content/user-research/guidelines/contents.lr index 66ad447..8a405b4 100644 --- a/content/user-research/guidelines/contents.lr +++ b/content/user-research/guidelines/contents.lr @@ -59,12 +59,11 @@ It is easier to have this material printed and in hands, but if you prefer, you Keep in mind that you might not have a useful Internet in the venue, so if you're going to install a Tor feature with someone during the interview, you may need to have it downloaded before the training. ## Report to Tor UX team -Before ending the training, coordinate with the trainer the feedbacks, you two should work together to hand out post-its for the audience; you can give one post-it on each color and ask them to fill it with what they think about: 1. the service they just learned; 2. Tor project; and 3. Tor, in general. It can also be questions - keep in mind that every feedback is proper feedback. +Before ending the training, coordinate with the trainer the feedbacks, you two should work together to hand out post-its for the audience, you can give one post-it on each color and ask them to fill it with what they think about: 1. the service they just learned; 2. Tor project; and 3. Tor in general. It can also be questions - keep in mind that every feedback is a good feedback. -We must hear back from you. We want to know how the training and the research were for you, how we can improve our support, and also if you're going to keep running Tor User Research. Please, fill out [this form](https://limesurvey), by the end of it, we will also ask your address to send to you a researcher kit (t-shirts and stickers). -We hope to hear back from you very soon! +It is very important for us to hear back from you. We want to know how the training and the research was for you, how we can improve our support and also, if you want to keep running Tor User Research. We will ask you to fill a form by the end of the research, so we can get your address to send to you a researcher kit (t-shirts and stickers). We hope to hear back from you very soon! -You can find our document to report [here](https://linkto). But if you think you won't have time to gather and report in this format, we would love to have another way to get the material you collected. You can take pictures or send your 'raw' notes for us. +We will send you our document on **how to report** to the UX team, so please [get in touch](https://lists.torproject.org/cgi-bin/mailman/listinfo/ux) with us to get it. If you think you won't have time to gather and report in this format, we would love to have another way to get the material you collected. You can take pictures or send your ´raw´ notes for us. ## Additional links

1 0

[community/staging] sentence in one line
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 7269fb0c0d784130a170de0f3f1c7c0e9e8c98cb Author: emma peel <emma.peel(a)riseup.net> Date: Wed Apr 8 11:04:36 2020 +0200 sentence in one line --- .../community-resources/tor-abuse-templates/contents.lr | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index e3b67a3..d66ede9 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -32,16 +32,14 @@ All templates should include the Common Boilerplate below, and append some addit The IP address in question is a Tor exit node. https://www.torproject.org/overview.html -There is little we can do to trace this matter further. As can be seen from the overview page, the Tor network is designed to make tracing of -users impossible. The Tor network is run by some 5000 volunteers who use the free software provided by the Tor Project to run Tor routers. +There is little we can do to trace this matter further. As can be seen from the overview page, the Tor network is designed to make tracing of users impossible. The Tor network is run by some 5000 volunteers who use the free software provided by the Tor Project to run Tor routers. Client connections are routed through multiple relays, and are multiplexed together on the connections between relays. The system does not record logs of client connections or previous hops. This is because the Tor network is a censorship resistance, privacy, and anonymity system used by whistle blowers, journalists, Chinese dissidents skirting the Great Firewall, abuse victims, stalker targets, the US military, and law enforcement, just to name a few. See https://www.torproject.org/about/torusers.html.en for more info. -Unfortunately, some people misuse the network. However, compared to the rate of legitimate use (the IP range in question processes nearly -a gigabit of traffic per second), [abuse complaints are rare](https://www.torproject.org/docs/faq-abuse.html.en). +Unfortunately, some people misuse the network. However, compared to the rate of legitimate use (the IP range in question processes nearly a gigabit of traffic per second), [abuse complaints are rare](https://www.torproject.org/docs/faq-abuse.html.en). ``` ## Abuse Scenarios

1 0

[community/staging] improve translators onboarding order, added irc channel
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 07e69fe7a82dd8429ce956a4b8089deb7b168ac7 Author: emma peel <emma.peel(a)riseup.net> Date: Fri Jan 10 13:00:44 2020 +0100 improve translators onboarding order, added irc channel --- content/localization/becoming-tor-translator/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/localization/becoming-tor-translator/contents.lr b/content/localization/becoming-tor-translator/contents.lr index 38ef805..9b348a3 100644 --- a/content/localization/becoming-tor-translator/contents.lr +++ b/content/localization/becoming-tor-translator/contents.lr @@ -20,7 +20,7 @@ Thank you for your interest in helping us with translations. # Localization mailing list <a name="tor-l10n" /> -To communicate with other translators, please join the [Tor localization mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n), where we organize translations, report errors in source strings, make final copy decisions, and address issues that arise. Please introduce yourself and ask any questions you may have after following up this instructions. +To communicate with other translators, please join the [Tor localization mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n), where we organize translations, take decisions, report errors in source strings, etc. Please introduce yourself and ask any questions you may have after following up this instructions. # Translation platform

1 0

[community/staging] Change dragonflybsd to look like debian step by step
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 7bc76d9880b05f5fafeebb2e35ba4705e28ead67 Author: gus <gus(a)torproject.org> Date: Fri Apr 10 21:36:18 2020 -0400 Change dragonflybsd to look like debian step by step --- .../technical-setup/guard/dragonflybsd/contents.lr | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/dragonflybsd/contents.lr b/content/relay-operations/technical-setup/guard/dragonflybsd/contents.lr index 8218178..d2934fe 100644 --- a/content/relay-operations/technical-setup/guard/dragonflybsd/contents.lr +++ b/content/relay-operations/technical-setup/guard/dragonflybsd/contents.lr @@ -46,9 +46,9 @@ pkg update -f pkg upgrade -y -f ``` -# 2. Install `tor` DragonflyBSD's Package +# 2. Package Installation -Here we can choose to install the latest stable version, like: +Install the `tor` package: ``` pkg install tor @@ -61,20 +61,24 @@ pkg install tor pkg install tor-devel ``` -# 3. Configure `/usr/local/etc/tor/torrc` +# 3. Configuration File + +Put the configuration file `/usr/local/etc/tor/torrc` in place: -This is a very simple version of the `torrc` configuration file in order to run a Middle/Guard relay on the Tor network: ``` -Nickname myBSDRelay # Change your relay's nickname to something you like -ContactInfo your@email # Please write your email address and be aware that it will be published -ORPort 443 # You might want to use/try a different port, should you want to +#change the nickname "myBSDrelay" to a name that you like +Nickname myBSDRelay +# You might want to use/try a different port, should you want to +ORPort 443 ExitRelay 0 SocksPort 0 Log notice syslog +# Change the email address below and be aware that it will be published +ContactInfo tor-operator@your-emailaddress-domain ``` -# 4. Start `tor`: +# 4. Start the service Here we set `tor` to start at boot time and use the setuid feature, in order to bind to lower ports like 443 (the daemon itself will still run as a regular non-privileged user).

1 0

[community/staging] Add printable outreach materials
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 14bbc3b24fc29135d5e2d38ee3985da348b141c7 Author: Pili Guerra <pili(a)piliguerra.com> Date: Wed Apr 8 18:32:23 2020 +0100 Add printable outreach materials Closes #28 --- content/outreach/kit/contents.lr | 2 +- databags/outreach-materials.ini | 54 +++++++++++++++++++++++++++++++++++++++ templates/outreach-materials.html | 36 ++++++++++++++++++++++++++ 3 files changed, 91 insertions(+), 1 deletion(-) diff --git a/content/outreach/kit/contents.lr b/content/outreach/kit/contents.lr index 59e782a..7f00085 100644 --- a/content/outreach/kit/contents.lr +++ b/content/outreach/kit/contents.lr @@ -12,7 +12,7 @@ subtitle: This kit includes printable flyers, stickers, and other materials to g --- key: 1 --- -html: two-columns-page.html +html: outreach-materials.html --- body: diff --git a/databags/outreach-materials.ini b/databags/outreach-materials.ini new file mode 100644 index 0000000..178b23b --- /dev/null +++ b/databags/outreach-materials.ini @@ -0,0 +1,54 @@ +[anti-censorship] +location = https://gitlab.torproject.org/torproject/community/outreach/-/raw/master/pr… +filename_front = Front_anti-censorship_en_EN.pdf +filename_back = Back_stencil_en_EN.pdf +label = Tor for Anti-censorship +type = handout +year = 2019 + +[feminists] +location = https://gitlab.torproject.org/torproject/community/outreach/-/raw/master/pr… +filename_front = Front_feminist_en_EN.pdf +filename_back = Back_feminist_en_EN.pdf +label = Tor for Feminists +type = handout +year = 2019 + +[human-rights] +location = https://gitlab.torproject.org/torproject/community/outreach/-/raw/master/pr… +filename_front = Front_humanrights_en_EN.pdf +filename_back = Back_stencil_en_EN.pdf +label = Tor for Human Rights +type = handout +year = 2019 + +[privacy] +location = https://gitlab.torproject.org/torproject/community/outreach/-/raw/master/pr… +filename_front = Front_privacy_en_EN.pdf +filename_back = Back_stencil_en_EN.pdf +label = Tor for Privacy +type = handout +year = 2019 + +[one-pager] +location = https://media.torproject.org/misc/ +filename_front = 2018-08-Tor-one-pager.pdf#page=1 +filename_back = 2018-08-Tor-one-pager.pdf#page=2 +label = Tor one pager +type = handout +year = 2018 + +[relay] +location = https://gitlab.torproject.org/torproject/ux/media/-/raw/master/outreach-mat… +filename_front = tor-relay_4.25x11_card_front.jpg +filename_back = tor-relay-4.25x11_card_back.jpg +label = Run a relay +type = handout +year = 2018 + +[brochure] +location = https://media.torproject.org/misc/2015-03-tor-brochure/ +filename = tor-brochure-en.pdf +label = Tor Brochure +type = brochure +year = 2015 \ No newline at end of file diff --git a/templates/outreach-materials.html b/templates/outreach-materials.html new file mode 100644 index 0000000..d0bdaa8 --- /dev/null +++ b/templates/outreach-materials.html @@ -0,0 +1,36 @@ +<div class="row pt-5"> + {% include 'sidenav.html' %} + <div class="col-sm-12 col-xs-12 ml-sm-auto col-md-9 col-lg-9 {{ bag('alternatives', this.alt, 'order') }}"> + {{ this.body }} + <div class="container py-3"> + <div class="row"> + <table class="table"> + <thead> + <tr> + <th scope="col">Title</th> + <th scope="col">Type</th> + <th scope="col">Links</th> + <th scope="col">Last Updated</th> + </tr> + </thead> + <tbody> + {% for id, item in bag('outreach-materials').items() %} + <tr> + <td>{{ item.label }}</td> + <td>{{ item.type }}</td> + <td> + {% if item.type=='handout' %} + <a href="{{item.location}}{{item.filename_front}}">Front</a> / <a href="{{item.location}}{{item.filename_back}}">Back</a> + {% else %} + <a href="{{item.location}}{{item.filename}}">File</a> + {% endif %} + </td> + <td>{{ item.year }}</td> + </tr> + {% endfor %} + </tbody> + </table> + </div> + </div> + </div> +</div> \ No newline at end of file

1 0

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

21 Mar '21

commit 4b35104a28b655963fb3cde20c6cc0c0ef3c040e Author: gus <gus(a)torproject.org> Date: Fri Apr 10 21:12:56 2020 -0400 Fix another typo --- .../relay-operations/technical-setup/guard/debianubuntu/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr b/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr index 851d399..56d4401 100644 --- a/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr +++ b/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr @@ -8,7 +8,7 @@ body: # 1. Enable Automatic Software Updates -One of the most imported things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. +One of the most important things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. # 2. Configure Tor Package Repository @@ -31,7 +31,7 @@ ORPort 443 ExitRelay 0 SocksPort 0 ControlSocket 0 -# Change the email address bellow and be aware that it will be published +# Change the email address below and be aware that it will be published ContactInfo tor-operator@your-emailaddress-domain ```

1 0

[community/staging] Fix consistency across headers
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit b2ca078543d9ad2c03cc0a6616a2be43f91e07a2 Author: Antonela <hola(a)antonela.me> Date: Mon Apr 13 13:12:22 2020 -0300 Fix consistency across headers Close https://gitlab.torproject.org/torproject/web/community/-/issues/124 --- content/relay-operations/technical-considerations/contents.lr | 2 ++ content/relay-operations/technical-setup/bridge/contents.lr | 9 +++++---- .../technical-setup/bridge/post-install/contents.lr | 9 ++++++--- .../relay-operations/technical-setup/post-install/contents.lr | 5 ++++- 4 files changed, 17 insertions(+), 8 deletions(-) diff --git a/content/relay-operations/technical-considerations/contents.lr b/content/relay-operations/technical-considerations/contents.lr index d2760c0..33ae63e 100644 --- a/content/relay-operations/technical-considerations/contents.lr +++ b/content/relay-operations/technical-considerations/contents.lr @@ -2,6 +2,8 @@ _model: page --- title: Technical considerations --- +color: primary +--- _template: layout.html --- body: diff --git a/content/relay-operations/technical-setup/bridge/contents.lr b/content/relay-operations/technical-setup/bridge/contents.lr index c1175cd..54a8c35 100644 --- a/content/relay-operations/technical-setup/bridge/contents.lr +++ b/content/relay-operations/technical-setup/bridge/contents.lr @@ -1,14 +1,12 @@ _model: page --- -title: - - Bridge +title: Bridge --- body: This guide will help you set up an obfs4 bridge to help censored users connect to the Tor network. The requirements are: 1. 24/7 Internet connectivity -2. The ability to expose TCP ports to the Internet (make sure that NAT doesn't get in the way) +2. The ability to expose TCP ports to the Internet (make sure that NAT doesn't get in the way) Note: If you're running a platform that is not listed on this page, you can [compile obfs4 from source](https://gitlab.com/yawning/obfs4#installation). --- @@ -23,3 +21,6 @@ section_id: bridge-operations subtitle: Run an obfs4 bridge to help censored users connect to the Tor network --- _slug: {{bridge}} +--- +color: primary +--- diff --git a/content/relay-operations/technical-setup/bridge/post-install/contents.lr b/content/relay-operations/technical-setup/bridge/post-install/contents.lr index d95da88..4abc2ea 100644 --- a/content/relay-operations/technical-setup/bridge/post-install/contents.lr +++ b/content/relay-operations/technical-setup/bridge/post-install/contents.lr @@ -4,17 +4,17 @@ title: Post-install --- body: -Congrats! +Congrats! If you get to this point, it means that your obfs4 bridge is running and is being distributed by BridgeDB to censored users. Note that it can take several days or weeks until you see a consistent set of users, so don't get discouraged if you don't see user connections right away. BridgeDB uses four buckets for bridge distribution: HTTPS, Moat, Email, and manual. Some buckets are used more than others, which also affects the time until your bridge sees users. Finally, there aren't many bridge users out there, so you cannot expect your bridge to be as popular as a relay. -If you want to connect to your bridge manually, you will need to know the bridge's obfs4 certificate. See the file `/var/lib/tor/pt_state/obfs4_bridgeline.txt` and paste the entire bridge line into Tor Browser: +If you want to connect to your bridge manually, you will need to know the bridge's obfs4 certificate. See the file `/var/lib/tor/pt_state/obfs4_bridgeline.txt` and paste the entire bridge line into Tor Browser: ``` Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0 ``` -You'll need to replace `<IP ADDRESS>`, `<PORT>`, and `<FINGERPRINT>` with the actual values, which you can find in the tor log. Make sure to use `<FINGERPRINT>`, not `<HASHED FINGERPRINT>`; and that `<PORT>` is the obfs4 port you chose - and not the OR port. +You'll need to replace `<IP ADDRESS>`, `<PORT>`, and `<FINGERPRINT>` with the actual values, which you can find in the tor log. Make sure to use `<FINGERPRINT>`, not `<HASHED FINGERPRINT>`; and that `<PORT>` is the obfs4 port you chose - and not the OR port. Finally, you can monitor your obfs4 bridge's usage on [Relay Search](https://metrics.torproject.org/rs.html#search). Just enter your bridge's `<HASHED FINGERPRINT>` in the form and click "Search". After having set up the bridge, it takes approximately three hours for the bridge to show up in Relay Search. @@ -24,3 +24,6 @@ html: two-columns-page.html key: 6 --- subtitle: How to find your bridge in Relay Search and connect manually +--- +color: primary +--- diff --git a/content/relay-operations/technical-setup/post-install/contents.lr b/content/relay-operations/technical-setup/post-install/contents.lr index 5236fbe..92441da 100644 --- a/content/relay-operations/technical-setup/post-install/contents.lr +++ b/content/relay-operations/technical-setup/post-install/contents.lr @@ -176,4 +176,7 @@ section: Relay operations --- section_id: relay-operations --- -subtitle: +subtitle: +--- +color: primary +---

1 0

[community/staging] Merge branch 'onions'
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 8986ed18cfc22001e6a28fb2669b05000a8ac6cf Merge: fda798c 655d2cb Author: gus <gus(a)torproject.org> Date: Fri Apr 10 13:46:19 2020 -0400 Merge branch 'onions' assets/static/images/onions/png/globaleaks.png | Bin 0 -> 52806 bytes assets/static/images/onions/png/onionshare.png | Bin 0 -> 16103 bytes assets/static/images/onions/png/securedrop.png | Bin 0 -> 17483 bytes databags/onion-tools.ini | 17 +++++++++++++++++ templates/onion-services.html | 17 +++++++++++++++++ 5 files changed, 34 insertions(+)

1 0

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

21 Mar '21

commit c2a65abeabcc820797e764540b45b32bc6218ea3 Author: gus <gus(a)torproject.org> Date: Fri Apr 10 21:10:49 2020 -0400 Fix a typo --- content/relay-operations/community-resources/bad-relays/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/bad-relays/contents.lr b/content/relay-operations/community-resources/bad-relays/contents.lr index 594eaf6..0a03c6f 100644 --- a/content/relay-operations/community-resources/bad-relays/contents.lr +++ b/content/relay-operations/community-resources/bad-relays/contents.lr @@ -41,7 +41,7 @@ However, if you need help with anything Tor-related, please contact the [help de After a relay is reported and we've verified the behavior we'll attempt to contact the relay operator. Often we can sort things out but if not (or the relay lacks contact information) we'll flag it to prevent it from continuing to be used. -We have thee types of flags we can apply: +We have three types of flags we can apply: * BadExit - Never used as an exit relay (for relays that appear to mess with exit traffic) * Invalid - Never used unless AllowInvalidNodes is set (by default this only allows for middle and rendezvous usage)

1 0

[community/staging] Add Tools section to Onion Services landing page. Fixes #66.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 655d2cbcf4715b00955530c5d4055df77b3138bc Author: Pili Guerra <pili(a)piliguerra.com> Date: Mon Mar 23 17:18:36 2020 +0000 Add Tools section to Onion Services landing page. Fixes #66. --- assets/static/images/onions/png/globaleaks.png | Bin 0 -> 52806 bytes assets/static/images/onions/png/onionshare.png | Bin 0 -> 16103 bytes assets/static/images/onions/png/securedrop.png | Bin 0 -> 17483 bytes databags/onion-tools.ini | 17 +++++++++++++++++ templates/onion-services.html | 17 +++++++++++++++++ 5 files changed, 34 insertions(+) diff --git a/assets/static/images/onions/png/globaleaks.png b/assets/static/images/onions/png/globaleaks.png new file mode 100644 index 0000000..d743c43 Binary files /dev/null and b/assets/static/images/onions/png/globaleaks.png differ diff --git a/assets/static/images/onions/png/onionshare.png b/assets/static/images/onions/png/onionshare.png new file mode 100644 index 0000000..e2948b0 Binary files /dev/null and b/assets/static/images/onions/png/onionshare.png differ diff --git a/assets/static/images/onions/png/securedrop.png b/assets/static/images/onions/png/securedrop.png new file mode 100644 index 0000000..55f9b01 Binary files /dev/null and b/assets/static/images/onions/png/securedrop.png differ diff --git a/databags/onion-tools.ini b/databags/onion-tools.ini new file mode 100644 index 0000000..d37dc3b --- /dev/null +++ b/databags/onion-tools.ini @@ -0,0 +1,17 @@ +[onionshare] +link = https://onionshare.org/ +image = /static/images/onions/png/onionshare.png +label = OnionShare +active = True + +[securedrop] +link = https://securedrop.org +image = /static/images/onions/png/securedrop.png +label = SecureDrop +active = True + +[globaleaks] +link = https://www.globaleaks.org/ +image =/static/images/onions/png/globaleaks.png +label= GlobaLeaks +active = True diff --git a/templates/onion-services.html b/templates/onion-services.html index a4a7ed6..2362213 100644 --- a/templates/onion-services.html +++ b/templates/onion-services.html @@ -50,6 +50,23 @@ </div> </div> {% endfor %} + </div> + <div class="row py-5 text-center mx-auto"> + <h2 class="display-4 text-primary text-center mx-auto">{{ _('Tools') }}</h2> + </div> + <div class="row mx-auto d-flex flex-wrap align-items-center"> + {% for id, item in bag('onion-tools').items() %} + {% if item.active == "True" %} + <div class="col-4"> + <div class="card h-50 border-0"> + <a href="{{ item.link }}"><img class="card-img-top h-100 w-50 mx-auto d-block" src="{{ item.image|asseturl }}"></a> + <div class="card-body"> + <p class="card-text text-primary text-center"><a href="{{ item.link }}">{{ item.label }}</a></p> + </div> + </div> + </div> + {% endif %} + {% endfor %} </div> <div class="row py-5 text-center mx-auto"> <h2 class="display-4 text-primary text-center mx-auto my-3">{{ _('Learn More') }}</h2>

1 0