The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-11-03T22:44:22Zhttps://gitlab.torproject.org/tpo/team/-/issues/41TPA-RFC-18: Tor security policy2023-11-03T22:44:22ZtraumschuleTPA-RFC-18: Tor security policyTor Project currently has not general security policy. We need to work out a security policy that covers all of Tor:
See https://trac.torproject.org/projects/tor/ticket/13968#comment:27Tor Project currently has not general security policy. We need to work out a security policy that covers all of Tor:
See https://trac.torproject.org/projects/tor/ticket/13968#comment:27https://gitlab.torproject.org/tpo/web/support/-/issues/242[lektor] software latest version macros for documentation to be always updated2023-12-04T12:25:03Zemmapeel[lektor] software latest version macros for documentation to be always updatedWhile writing docs we have some strings that change in each release. Having some sort of macro will help documentation stay updated and the editors will have more time to improve other things.
### Latest versions for software
One nice ...While writing docs we have some strings that change in each release. Having some sort of macro will help documentation stay updated and the editors will have more time to improve other things.
### Latest versions for software
One nice macro should give, in a string, the last Tor Browser version, for example in the string: `tor-browser-linux64-10.0.14_zh-CN.tar.xz` it will be `10.0.14`.
So, we could write 'download Tor Browser i.e. tor-browser-linux64-[!latest_tbb]_zh-CN.tar.xz' or 'Are you using the current Tor Browser ([!latest_tbb])?'.
The most clever thing will be to take this information from the corresponding databags (https://gitweb.torproject.org/project/web/tpo.git/tree/databags/ ) so we dont risk to become outdated, and we dont add more tasks to the release process.https://gitlab.torproject.org/tpo/web/manual/-/issues/99Update known issues page - Tor Browser desktop and mobile2024-01-30T13:40:21ZGusUpdate known issues page - Tor Browser desktop and mobileAccording to the [blog post](https://blog.torproject.org/new-release-tor-browser-105), here's a list of known issues that we need to update the Tor Browser Manual:
### Desktop
- tpo/applications/tor-browser#40497
- tpo/applications/tor...According to the [blog post](https://blog.torproject.org/new-release-tor-browser-105), here's a list of known issues that we need to update the Tor Browser Manual:
### Desktop
- tpo/applications/tor-browser#40497
- tpo/applications/tor-browser#40242
- tpo/applications/tor-browser#40506
- tpo/applications/tor-browser#40510
https://tb-manual.torproject.org/known-issues/
### Mobile
- tpo/applications/fenix#40176
- tpo/applications/fenix#40110
- tpo/applications/fenix#40172
- tpo/applications/fenix#40174
- tpo/applications/fenix#40103
- tpo/applications/fenix#40115
- tpo/applications/fenix#40324
https://tb-manual.torproject.org/mobile-tor/ebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/229Add "You should split each connection over many paths"2023-11-12T01:26:32ZGusAdd "You should split each connection over many paths"The answer should mention Network Team new research about traffic congestion.
https://2019.www.torproject.org/docs/faq.html.en#SplitEachConnection
We don't currently think this is a good idea. You see, the attacks we're worried about a...The answer should mention Network Team new research about traffic congestion.
https://2019.www.torproject.org/docs/faq.html.en#SplitEachConnection
We don't currently think this is a good idea. You see, the attacks we're worried about are at the endpoints: the adversary watches Alice (or the first hop in the path) and Bob (or the last hop in the path) and learns that they are communicating.
If we make the assumption that timing attacks work well on even a few packets end-to-end, then having *more* possible ways for the adversary to observe the connection seems to hurt anonymity, not help it.
Now, it's possible that we could make ourselves more resistant to end-to-end attacks with a little bit of padding and by making each circuit send and receive a fixed number of cells. This approach is more well-understood in the context of high-latency systems. See e.g. Message Splitting Against the Partial Adversary by Andrei Serjantov and Steven J. Murdoch.
But since we don't currently understand what network and padding parameters, if any, could provide increased end-to-end security, our current strategy is to minimize the number of places that the adversary could possibly see.https://gitlab.torproject.org/tpo/web/support/-/issues/203add explanation about disabled Master Password, on support portal or ideally ...2023-11-13T13:44:30Zemmapeeladd explanation about disabled Master Password, on support portal or ideally in tor browser itselfA user entered today on the irc asking how could they add a master password to the Tor Browser. It seems a common doubt for new users.
Proposal:
- Maybe it will be good to have an official explanation on our Support portal about why the...A user entered today on the irc asking how could they add a master password to the Tor Browser. It seems a common doubt for new users.
Proposal:
- Maybe it will be good to have an official explanation on our Support portal about why there is no master password in Tor Browser?
From the Tor Browser Design Draft (https://2019.www.torproject.org/projects/torbrowser/design/):
We disable the password saving functionality in the browser as part of our Disk Avoidance requirement. However, since users may decide to re-enable disk history records and password saving, we also set the signon.autofillForms preference to false to prevent saved values from immediately populating fields upon page load. Since JavaScript can read these values as soon as they appear, setting this preference prevents automatic linkability from stored passwords.
(we should write a more simple answer)https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40004Write 'survival guide' for keeping metrics website up2023-01-23T14:53:51ZRoger DingledineWrite 'survival guide' for keeping metrics website upopara pointed out today that metrics.torproject.org was returning 503's.
I logged in to the server, saw that the server and apache were working fine, found a proxypass stanza in the apache config, noticed that there was a /home/metrics/...opara pointed out today that metrics.torproject.org was returning 503's.
I logged in to the server, saw that the server and apache were working fine, found a proxypass stanza in the apache config, noticed that there was a /home/metrics/, and looked through the end of /home/metrics/.bash_history to make some guesses about what to run to get things working again. It seems to be back and working (I did a "sudo -s -H -u metrics" because I saw karsten had run that, and then "./start-web.sh" and eventually decided to background it when it never exited.)
It would be great to make a 'survival guide' wiki page for it, like<br>
https://gitlab.torproject.org/tpo/metrics/team/-/wikis/Survival-Guides/Exit-Scanner
And then link to it from tpo/tpa/team#40045 so we can use it next time.
Thanks!https://gitlab.torproject.org/tpo/core/tor/-/issues/32863Put an up-to-date web version of the Tor manual somewhere2022-06-10T19:45:23ZRoger DingledinePut an up-to-date web version of the Tor manual somewhereWe used to publish
https://2019.www.torproject.org/docs/tor-manual.html.en
but that version of the Tor manual is now obsolete and for archival purposes.
I guess in the glorious future we will have a dev.torproject.org/tor/ that lists th...We used to publish
https://2019.www.torproject.org/docs/tor-manual.html.en
but that version of the Tor manual is now obsolete and for archival purposes.
I guess in the glorious future we will have a dev.torproject.org/tor/ that lists things like the Tor manual. Or maybe it should be on support.torproject.org because it is a resource for users (albeit advanced ones), not developers. Maybe it *is* on support.tpo right now, and I just couldn't find it?
In any case, here is a ticket for making progress on actually getting a web version of the manual onto a web page somewhere, ideally automatically kept up to date.
(Once it exists, there is a good argument for adding another htaccess rule to the 2019.www site, redirecting from the man page that nobody should look at it to the one that people should.)
This ticket motivated by discussion in legacy/trac#28526.Developer portalhttps://gitlab.torproject.org/tpo/core/tor/-/issues/12138No IPv6 support when suggesting a bindaddr to a PT2022-02-28T19:40:20ZGeorge KadianakisNo IPv6 support when suggesting a bindaddr to a PTThis recent post in tor-talk:
http://www.marshut.com/iwuqqh/setting-up-an-ipv6-%20supporting-obfs3-bridge.html
revealed that Tor does not support IPv6 when supporting a bind address to a pluggable transport. It seems that we missed that ...This recent post in tor-talk:
http://www.marshut.com/iwuqqh/setting-up-an-ipv6-%20supporting-obfs3-bridge.html
revealed that Tor does not support IPv6 when supporting a bind address to a pluggable transport. It seems that we missed that during legacy/trac#7011.
The problem is that the first time someone fires up a `ServerTransportPlugin`, Tor will suggest to it to bind in `0.0.0.0:0`. This can be seen in `get_stored_bindaddr_for_server_transport`:
https://gitweb.torproject.org/tor.git/blob/2ee56e4c2c841a45418cfb826e1ce6689278382d:/src/or/statefile.c#l517
```
no_bindaddr_found:
/** If we didn't find references for this pluggable transport in the
state file, we should instruct the pluggable transport proxy to
listen on INADDR_ANY on a random ephemeral port. */
tor_asprintf(&default_addrport, "%s:%s", fmt_addr32(INADDR_ANY), "0");
return default_addrport;
```
Instead of using `fmt_addr32(INADDR_ANY)`, we should use `fmt_addrport` and suggest `[::]` if we need to use IPv6. We should probably suggest an IPv6 address, if our ORPort is IPv6 (what if we have both kinds of ORPorts?).
Implementation of this should not be hard. I can do it one of these days.Alexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/90Improve verifying signatures instructions, especially on Windows2023-11-12T20:12:23ZHiroImprove verifying signatures instructions, especially on WindowsFrom: https://trac.torproject.org/projects/tor/ticket/33529
The instructions on verifying signatures at https://support.torproject.org/tbb/how-to-verify-signature/ should be clearer and more concise.
A frontdesk email reads:
"In orde...From: https://trac.torproject.org/projects/tor/ticket/33529
The instructions on verifying signatures at https://support.torproject.org/tbb/how-to-verify-signature/ should be clearer and more concise.
A frontdesk email reads:
"In order to verify the integrity of the Tor browser installation file, you recommend downloading GPG4win, but then your instructions for Windows say to use a command line command that is not included with that package, and there are no instructions on how to use the GUI to verify the package (or which GUI to use, since there are at least two included in GPG4win).
https://support.torproject.org/tbb/how-to-verify-signature/
Trying to import the asc file into Kleopatra or the GNU Privacy Assistant results in a message saying that 0 certificates were imported, or no keys were found.
What's more, there is a confusing reference to the " Tor Browser Developers signing key (0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290)". Is this the key I'm supposed to be using for verification? This doesn't appear to be a PGP public key.
There's also a statement that suggests that the PGP public key file is automatically downloaded with the installation package, but it's not. "Each file on our download page is accompanied by a file with the same name as the package and the extension ".asc"." The download page does not show file names, and using the download link on the download page only downloads the exe file."https://gitlab.torproject.org/tpo/community/team/-/issues/8Template letter to universities to unblock Tor2023-11-24T11:56:40ZGusTemplate letter to universities to unblock TorSome universities are blocking torproject.org and also the Tor network.
If we create a template letter, I think many students and teachers will feel engaged to formalize and fill some papers to request to unblock Tor at their universiti...Some universities are blocking torproject.org and also the Tor network.
If we create a template letter, I think many students and teachers will feel engaged to formalize and fill some papers to request to unblock Tor at their universities. And even if the university doesn't unblock at least it will require a formal answer from the university. Thoughts?Roger DingledineRoger Dingledine2023-12-01https://gitlab.torproject.org/tpo/web/support/-/issues/65Add question: "What's the difference between Tor and DoH (DNS over HTTPS)?" t...2022-01-20T19:20:30ZGusAdd question: "What's the difference between Tor and DoH (DNS over HTTPS)?" to HTTPS sectionRef: Discussion about Tor Browser and DNS over HTTPS : https://trac.torproject.org/projects/tor/ticket/30753Ref: Discussion about Tor Browser and DNS over HTTPS : https://trac.torproject.org/projects/tor/ticket/30753https://gitlab.torproject.org/tpo/web/support/-/issues/20Improve NoScript documentation2022-02-15T20:01:35ZAntonelaantonela@torproject.orgImprove NoScript documentation[https://blog.torproject.org/comment/277954#comment-277954 A user asks] for a better documentation for NoScript 10.
> On the introductory page you have a link "FAQ", and there you will find a link "NoScript FAQ", which will open the FAQ ...[https://blog.torproject.org/comment/277954#comment-277954 A user asks] for a better documentation for NoScript 10.
> On the introductory page you have a link "FAQ", and there you will find a link "NoScript FAQ", which will open the FAQ for the old noscript version(s). There is no official documentation for noscript. All you can get is a link to a blog writer giving "basic" information about the new noscript. This is very basic indeed and not an official documentation.
> Another link will redirect you to a page inteding to give an overview of the new noscript in a nutshell. A nutshell is not enough for understanding the new noscript - as you can see from the "226 Responses to “NoScript, "Quantum" vs "Legacy" in a nutshell”.
The [https://www.torproject.org/docs/faq current/old FAQ] does not link the NoScript FAQ, while the [https://support.torproject.org/#tbb support page] does.
[https://support.torproject.org/#tbb-25 I'm having a problem with NoScript.] links to the NoScript FAQ which i think is fine although it may not reflect [https://noscript.net/changelog latest changes]?
BTW {{{Should I install a new add-on or extension in Tor Browser, like AdBlock Plus or uBlock Origin?}}} is listed twice ([https://support.torproject.org/#faq-3 faq-3] and [https://support.torproject.org/#tbb-14 tbb-14])
https://trac.torproject.org/projects/tor/ticket/28418https://gitlab.torproject.org/tpo/onion-services/onionspray/-/issues/51Improved troubleshooting tips2024-03-28T13:07:39ZSilvio RhattoImproved troubleshooting tips# Tasks
* [ ] Improve the "Troubleshooting" document with tips to debug Onionspray, NGINX and tor.
* [ ] Include debugging tips such as custom log configurations like `Log [rend]info notice file /var/log/tor/notices.log`
that can ...# Tasks
* [ ] Improve the "Troubleshooting" document with tips to debug Onionspray, NGINX and tor.
* [ ] Include debugging tips such as custom log configurations like `Log [rend]info notice file /var/log/tor/notices.log`
that can reduce the noise and pinpoint things (but usually is better to log all subsystems).
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Onionspray 1.7.0Silvio RhattoSilvio Rhatto2024-06-27https://gitlab.torproject.org/tpo/web/manual/-/issues/158Update instructions about using built-in bridges in Tor Browser2024-03-26T12:58:53Zebanamebanam@torproject.orgUpdate instructions about using built-in bridges in Tor Browserhttps://tb-manual.torproject.org/circumvention/
The UX has changed a bit. Let's review and update this section about using built-in bridges with Tor Browser.
> USING PLUGGABLE TRANSPORTS
>
> To use a pluggable transport, click "Configu...https://tb-manual.torproject.org/circumvention/
The UX has changed a bit. Let's review and update this section about using built-in bridges with Tor Browser.
> USING PLUGGABLE TRANSPORTS
>
> To use a pluggable transport, click "Configure Connection" when starting Tor Browser for the first time. Under the "Bridges" section, locate the option "Choose from one of Tor Browser's built-in bridges" and click on "Select a Built-In Bridge" option. From the menu, select whichever pluggable transport you'd like to use.
>
> Once you've selected the pluggable transport, scroll up and click "Connect" to save your settings.
>
> Or, if you have Tor Browser running, click on "Settings" in the hamburger menu (≡) and then on "Connection" in the sidebar. Under the "Bridges" section, locate the option "Choose from one of Tor Browser's built-in bridges" and click on "Select a Built-In Bridge" option. Choose whichever pluggable transport you'd like to use from the menu. Your settings will automatically be saved once you close the tab.
/cc @nina @emmapeelebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/web/manual/-/issues/157Add entry about letterboxing (about:manual#letterboxing)2024-03-12T20:36:03Zma1Add entry about letterboxing (about:manual#letterboxing)We're implementing a `Learn more` link in the new user-facing letteboxing preferences (tpo/applications/tor-browser#41916) and we need some content to be referenced by about:manual#letterboxing :)
@donuts' [comment](https://gitlab.torp...We're implementing a `Learn more` link in the new user-facing letteboxing preferences (tpo/applications/tor-browser#41916) and we need some content to be referenced by about:manual#letterboxing :)
@donuts' [comment](https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/32324#note_2876483):
> It's on support-dot, but possibly not the manual?
> https://support.torproject.org/tbb/maximized-torbrowser-window/ebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/6README update with maintenance instructions2024-02-29T12:45:41ZSilvio RhattoREADME update with maintenance instructions# Tasks
* [ ] Add into the [README](README.md):
* [ ] Onion Services doc conventions, including:
* Use the navigation format from the [mkdocs-awesome-pages-plugin][].
* Have `README.md` or `index.md` listed as the "Intro" page...# Tasks
* [ ] Add into the [README](README.md):
* [ ] Onion Services doc conventions, including:
* Use the navigation format from the [mkdocs-awesome-pages-plugin][].
* Have `README.md` or `index.md` listed as the "Intro" page.
* Have a link to the repository in the README/index page.
* [ ] How to contribute with new docs:
* Open an issue request or pull request for an evaluation/integration.
* [ ] How to integrate your existing docs:
* Need to be Onion Service related.
* Setup Onion MkDocs.
* Adopt the Onion Services doc conventions.
* Adhere to the Community Team docs guidelines.
* Open an issue request or pull request for an evaluation/integration.
[mkdocs-awesome-pages-plugin]: https://github.com/lukasgeiter/mkdocs-awesome-pages-plugin
# Time estimation
* Complexity: very small (0.5 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/5Slides generation2024-02-27T18:58:24ZSilvio RhattoSlides generation# Description
Some projects have [Onion TeX Slim][]-generated slides that could be built as part of this repository CI/CD.
[Onion TeX Slim]: https://gitlab.torproject.org/tpo/community/onion-tex-slim
# Tasks
* [ ] Create a convention...# Description
Some projects have [Onion TeX Slim][]-generated slides that could be built as part of this repository CI/CD.
[Onion TeX Slim]: https://gitlab.torproject.org/tpo/community/onion-tex-slim
# Tasks
* [ ] Create a convention for [Onion TeX Slim][] slides among Onion Service documentation (folder location etc).
* [ ] Implement a CI/CD action to generate all slides, including then in the generated documentation.
# Time estimation
* Complexity: small (1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)https://gitlab.torproject.org/tpo/web/snowflake/-/issues/9unify volunteer instructions from support entry onto snowflake website2024-02-27T14:24:07ZRoger Dingledineunify volunteer instructions from support entry onto snowflake websiteWe have this support entry: <br>
https://support.torproject.org/censorship/how-to-help-running-snowflake/
which tells people to install the Firefox or Chrome extension, or load the embed in a page. It doesn't mention the Edge extension ...We have this support entry: <br>
https://support.torproject.org/censorship/how-to-help-running-snowflake/
which tells people to install the Firefox or Chrome extension, or load the embed in a page. It doesn't mention the Edge extension or the standalone proxy.
Rather than trying to keep both sets of instructions in sync, I think we should put the instructions on the snowflake.torproject.org page, and point to them from a much slimmer support entry.
To achieve this goal, there are currently two things that the support entry says that the snowflake.torproject.org website does not:
* You need to enable WebRTC in your browser, to usefully run the extension or to usefully load the embed. (If we could reliably have the extension or the embed page report that your WebRTC is missing and you need to fix that, then we could get away with not saying it on the webpage. So, feel free to do that instead if it is easier, but I am suspecting it is not easier. :)
* "Due to censorship of VPN servers in some countries, we kindly ask you to not run a snowflake proxy while connected to a VPN" as advised by @cohosh at https://forum.torproject.org/t/running-a-snowflake-proxy-behind-a-vpn-consequences-for-tor-users/2047/4 and then recorded by gus at https://gitlab.torproject.org/tpo/web/support/-/issues/296. Feel free also to change your mind about the "not on a VPN please" advice.
Once we have these two items either make their way onto the snowflake.torproject.org proxy instructions or have you tell us you don't intend to, then we should be all ready to remove the (redundant, already not as correct) text from the support entry.
Thanks!https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/2Add Onionbalance documentation2024-03-27T21:34:58ZSilvio RhattoAdd Onionbalance documentation# Tasks
* [ ] Add the Onionbalance documentation once it's [converted to Onion MkDocs][].
[converted to Onion MkDocs]: tpo/onion-services/onionbalance#28
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
...# Tasks
* [ ] Add the Onionbalance documentation once it's [converted to Onion MkDocs][].
[converted to Onion MkDocs]: tpo/onion-services/onionbalance#28
# Time estimation
* Complexity: negligible (0.1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)Silvio RhattoSilvio Rhatto2024-07-01https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/1Hosting location for the Onion Services Ecosystem Documentation2024-03-27T22:03:23ZSilvio RhattoHosting location for the Onion Services Ecosystem Documentation# Motivation
As mentioned in the [previous issue][] about getting domains for some Onion Services projects, we're looking for
* Shorter URLs for some Onion Services related projects, pointing to their GitLab Pages.
* Aggregate Onion Se...# Motivation
As mentioned in the [previous issue][] about getting domains for some Onion Services projects, we're looking for
* Shorter URLs for some Onion Services related projects, pointing to their GitLab Pages.
* Aggregate Onion Services documentation in a single, searchable place.
That made us create the [Onion Services Ecosystem Documentation][], but it still has a not very friendly URL.
[previous issue]: tpo/onion-services/onion-support#202
[Onion Services Ecosystem Documentation]: https://tpo.pages.torproject.net/onion-services/ecosystem
# Tasks
* [x] Organization:
* [x] Ping some people to get feedback (ahf, gaba, micah?).
* [x] Determine a better canonical URL location for the [Onion Services Ecosystem Documentation][]:
* [x] Project/repository name: `tpo/onion-services/ecosystem`.
* [x] Canonical URL: `https://community.torproject.org/onion-services/ecosystem`.
* [x] Rename the project from `portal` to `ecosystem`.
* [ ] Implementation:
* [x] Proceed with the CI/deployment changes to make the [Onion Services Ecosystem Documentation][] accessible through the new URL:
* [~] Update CI config to use the [static shim][] deploying to the [static component]. No need, since we'll use the existing deployment from `tpo/web/community`.
* [x] Update CI config to use a setup [similiar to the Community Policies][] (tpo/onion-services/ecosystem!6).
* [x] Update [web/community CI config](https://gitlab.torproject.org/tpo/web/community/-/blob/main/.gitlab-ci.yml) to include the Ecosystem Docs (tpo/web/community!349).
* [~] [Ask TPA](https://gitlab.torproject.org/tpo/tpa/team/-/issues/new) to help with setting up this deployment. No need, since we'll use the existing deployment from `tpo/web/community`.
* [x] Update references in Onion Services projects, pointing to the new official/canonical documentation location (like on `README.md` files etc).
* [ ] Once the portal is deployed, updated the "Onionize any website" link in
the Community Portal, pointing to the official Onionspray documentation
URL within the Onion Services Ecosystem Portal (tpo/web/community#337).
* [ ] Link the [Onion Services Ecosystem Documentation] in the [Onion Services section of the Community Portal](https://community.torproject.org/onion-services/).
* [ ] Add banner in the community portal, at the [Onion Services page](https://community.torproject.org/onion-services/).
* [ ] Figure out [an update workflow](https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/1#note_3010677).
* [~] Bonus:
* [~] Consider to release the portal as part of the [Onion Services 20th Years Anniversary (2024 edition)](https://gitlab.torproject.org/tpo/onion-services/onionplan/-/issues/14#note_2933136).
* [~] Onion Services endpoint and Onion-Location set (if not already available). This will be available already when the docs are available through `community.torproject.org`.
[static shim]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/static-shim
[static component]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/static-component
[similiar to the Community Policies]: https://gitlab.torproject.org/tpo/community/policies/-/blob/main/.gitlab-ci.yml
# Time estimation
* Complexity: small (1 day)
* Uncertainty: low (x1.1)
* [Reference](https://jacobian.org/2021/may/25/my-estimation-technique/) (adapted)
/cc @gusSilvio RhattoSilvio Rhatto2024-06-17