The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-10-03T15:38:27Zhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40886Update README with instructions for Arch linux2023-10-03T15:38:27ZDan BallardUpdate README with instructions for Arch linuxI'm using Arch linux now, so there's a lot of packages to install to run RBM, I think I've collected them allI'm using Arch linux now, so there's a lot of packages to install to run RBM, I think I've collected them allDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/web/support/-/issues/330Mention that Orbot is no longer required to run Onion Browser on iOS2024-02-27T11:40:25Zebanamebanam@torproject.orgMention that Orbot is no longer required to run Onion Browser on iOSWith [version 3.0 of Onion Browser](https://github.com/OnionBrowser/OnionBrowser/issues/423), users also need to install Orbot. We should mention this in our documentation: "[Can I run Tor Browser on an iOS device?](https://support.torpr...With [version 3.0 of Onion Browser](https://github.com/OnionBrowser/OnionBrowser/issues/423), users also need to install Orbot. We should mention this in our documentation: "[Can I run Tor Browser on an iOS device?](https://support.torproject.org/tormobile/tormobile-3/)"
Update: It's no longer required to have Orbot + Onion Browser, but if you have Orbot installed, Onion Browser will ask permission to use it. We will need to update the documentation.ebanamebanam@torproject.orgebanamebanam@torproject.orghttps://gitlab.torproject.org/tpo/web/support/-/issues/329Review support entries for Tor Browser 12.5 release2023-06-23T14:57:09ZGusReview support entries for Tor Browser 12.5 releasechampionquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/web/manual/-/issues/147Update Tor Browser User Manual for the Tor Browser 12.5 release2023-06-20T14:34:20Zchampionquizzerchampionquizzer@torproject.orgUpdate Tor Browser User Manual for the Tor Browser 12.5 releaserelated to: https://gitlab.torproject.org/tpo/community/support/-/issues/40113related to: https://gitlab.torproject.org/tpo/community/support/-/issues/40113championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/community/team/-/issues/94Webtunnel soft release strategy2024-03-06T21:45:41ZGusWebtunnel soft release strategy## Phase 1 - Soft release
- [x] Present WebTunnel to the relay operators meetup and get some bridge operators running it (meetup June 2023: https://gitlab.torproject.org/tpo/community/relays/-/issues/70)
- [x] Help Bridge operators to d...## Phase 1 - Soft release
- [x] Present WebTunnel to the relay operators meetup and get some bridge operators running it (meetup June 2023: https://gitlab.torproject.org/tpo/community/relays/-/issues/70)
- [x] Help Bridge operators to deploy and debug their WebTunnel setup
- [x] Ask our user support team to give to some users in censored regions (https://gitlab.torproject.org/tpo/community/support/-/issues/40117)
- [x] Meet with AC-team to share feedback (during AC-Team weekly meeting in July)
## Phase 2 - Review documentation
- [x] Review operators feedback and move the bridge operators docs to the community portal - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtunnel/-/blob/main/README.md - https://gitlab.torproject.org/tpo/web/community/-/issues/320
## Phase 3 - Tor Browser stable
- [x] When WebTunnel move to Tor Browser Stable, write WebTunnel users docs (TB-Manual https://gitlab.torproject.org/tpo/web/manual/-/merge_requests/84, Support portal, Training materials)
- [x] Write and publish Call for testers (like Conjure call for testers, see https://gitlab.torproject.org/tpo/community/team/-/issues/88)
- [x] Call for new WebTunnel bridge operators - https://gitlab.torproject.org/tpo/community/relays/-/issues/69GusGushttps://gitlab.torproject.org/tpo/community/team/-/issues/93Onion Services PoW feature release strategy2023-09-25T16:04:26ZSilvio RhattoOnion Services PoW feature release strategyRelease strategy on the [PoW](tpo/core/tor#40634) protection:
* [x] Draft [Q&A][] for ext. inquiries (cc @rhatto).
* [x] Write the docs (handled on tpo/web/community#312).
* [x] Write a [call for ~testers~ operators](https://pad.riseup....Release strategy on the [PoW](tpo/core/tor#40634) protection:
* [x] Draft [Q&A][] for ext. inquiries (cc @rhatto).
* [x] Write the docs (handled on tpo/web/community#312).
* [x] Write a [call for ~testers~ operators](https://pad.riseup.net/p/powcallfortesters) for a forum post (how/where to test, submitting feedback etc) (audience: Onion Service operators). Consider using the [Conjure one](https://forum.torproject.net/t/call-for-testers-help-the-tor-project-to-test-conjure-on-tor-browser-alpha/7815) as a template.
* [x] Write a blog post to be released along with the stable; involve Comms team (cc @pavel).
* [x] Final fact check with the larger team.
* [x] Publish the [blog post][].
* [x] Publish the [forum post][].
* [x] Publish an additional ~forum post~ [wiki page][] with the full [Q&A][].
Feedback collection ([moved to another ticket](tpo/community/team#95)):
* [~] Report back ~"For Network Health Team" (via forum post comments and issues).
* [~] Update the [Support Portal](https://support.torproject.org/) with the questions most asked by users (instead of just including everything from the Q&A, which would increase the number of strings to translate).
[Q&A]: https://pad.riseup.net/p/powqna
[blog post]: https://blog.torproject.org/introducing-proof-of-work-defense-for-onion-services/
[forum post]: https://forum.torproject.org/t/proof-of-work-pow-defense-for-onion-service-is-released/8887
[wiki page]: https://gitlab.torproject.org/tpo/onion-services/onion-support/-/wikis/Documentation/PoW-FAQSilvio RhattoSilvio Rhatto2023-08-23https://gitlab.torproject.org/tpo/web/community/-/issues/314Onion Services PoW feature release strategy2023-06-15T14:48:08ZSilvio RhattoOnion Services PoW feature release strategyFeedback collection / release strategy on [PoW](tpo/core/tor#40634):
* [ ] Write the docs (handled on tpo/web/community#312).
* [ ] Create a forum post (how/where to test feedback etc) for operators. Use the [Conjure one](https://forum....Feedback collection / release strategy on [PoW](tpo/core/tor#40634):
* [ ] Write the docs (handled on tpo/web/community#312).
* [ ] Create a forum post (how/where to test feedback etc) for operators. Use the [Conjure one](https://forum.torproject.net/t/call-for-testers-help-the-tor-project-to-test-conjure-on-tor-browser-alpha/7815) as a template.
* [ ] Report back ~"For Network Health Team" (via forum post comments and issues).
* [ ] Write a blog post to be released along with the stable; involve Comms team.Silvio RhattoSilvio Rhatto2023-07-31https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40880The README doesn't include some dependencies needed for building incrementals2023-10-03T15:38:11ZPier Angelo VendrameThe README doesn't include some dependencies needed for building incrementalsIt seems we're missing at least `libxml-libxml-perl`, but possibly also `libxml-writer-perl` and `libparallel-forkmanager-perl`.
```
$ make mullvadbrowser-incrementals-release
git submodule update --init
./rbm/rbm build release --step u...It seems we're missing at least `libxml-libxml-perl`, but possibly also `libxml-writer-perl` and `libparallel-forkmanager-perl`.
```
$ make mullvadbrowser-incrementals-release
git submodule update --init
./rbm/rbm build release --step update_responses_config --target release --target create_unsigned_incrementals --target mullvadbrowser
tools/update-responses/download_missing_versions release
Can't locate XML/LibXML.pm in @INC (you may need to install the XML::LibXML module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 /usr/local/lib/site_perl) at tools/update-responses/download_missing_versions line 20.
BEGIN failed--compilation aborted at tools/update-responses/download_missing_versions line 20.
make: *** [Makefile:501: mullvadbrowser-incrementals-release] Error 2
```
/cc @boklmDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41188Migrate new machine docs to new swap file policy2023-05-25T15:05:34ZJérôme Charaouilavamind@torproject.orgMigrate new machine docs to new swap file policyFollowing adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should implement the changes to our new-machines documentation and templates.
- [x] new gane...Following adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should implement the changes to our new-machines documentation and templates.
- [x] new ganeti instance docs
- [x] new physical machine docs
- [x] fabric installer disk templatesJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41187Document swap file resizing2023-05-24T21:55:16ZJérôme Charaouilavamind@torproject.orgDocument swap file resizingFollowing adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should document how to resize the ganeti installer-created swap file for instances that requi...Following adoption of [TPA-RFC-55: Swap file policy](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-55-swap-file-policy), we should document how to resize the ganeti installer-created swap file for instances that require more swap space.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40866Remove `Using ansible to set up a nightly build machine` from README2023-06-07T21:43:13ZboklmRemove `Using ansible to set up a nightly build machine` from READMEIn aadd6feb0302552da49eac8cae440c1510a436f3 we removed
`tools/ansible/roles/tbb-nightly-build`, but forgot to remove the section
`Using ansible to set up a nightly build machine` in the README file.In aadd6feb0302552da49eac8cae440c1510a436f3 we removed
`tools/ansible/roles/tbb-nightly-build`, but forgot to remove the section
`Using ansible to set up a nightly build machine` in the README file.https://gitlab.torproject.org/tpo/web/community/-/issues/312User documentation related to the upcoming Onion Services PoW protection2023-08-16T12:23:06ZSilvio RhattoUser documentation related to the upcoming Onion Services PoW protectionCreate user documentation related to the upcoming Onion Services PoW protection (tpo/core/tor!702):
* [x] Sync with Network and Applications Team to coordinate this documentation with C Tor and Tor Browser releases implementing this fea...Create user documentation related to the upcoming Onion Services PoW protection (tpo/core/tor!702):
* [x] Sync with Network and Applications Team to coordinate this documentation with C Tor and Tor Browser releases implementing this feature.
* [x] Check the torspec, man page and the [onion-pow-example](https://gitlab.torproject.org/beth/onion-pow-example).
* [x] Test the feature. Moved to tpo/onion-services/onion-support#229.
* [x] Write/update the documentation:
* [x] Client side: what the users should know, need to do and possible issues (like PoW on low-end mobile devices) (this may go to a different ticket, possibly related to the Tor Browser manual). Being handled at tpo/community/team#93.
* [x] Handle tpo/core/torspec!153 and tpo/core/torspec!155.
* [x] Server side: steps to implement the PoW defense by Onion Service Operators at the [Onion service DoS guidelines][] page (tpo/web/community!313).
[Onion service DoS guidelines]: https://community.torproject.org/onion-services/advanced/dos/
References:
* [Tor Browser build with PoW support](https://gitlab.torproject.org/beth/tor-browser-build/-/tree/torbrowser-with-pow?ref_type=heads)
* [onion-pow-example](https://gitlab.torproject.org/beth/onion-pow-example)
/cc @gusSilvio RhattoSilvio Rhatto2023-08-16https://gitlab.torproject.org/tpo/web/support/-/issues/327Dead link to blog2023-11-06T19:25:02ZslrslrDead link to bloghttps://support.torproject.org/tbb/tbb-22/
contains 404 not found link to https://blog.torproject.org/why-tor-is-slow
It is not even on archive: https://web.archive.org/web/20220715000000*/https://blog.torproject.org/why-tor-is-slow
I a...https://support.torproject.org/tbb/tbb-22/
contains 404 not found link to https://blog.torproject.org/why-tor-is-slow
It is not even on archive: https://web.archive.org/web/20220715000000*/https://blog.torproject.org/why-tor-is-slow
I am unsure if the article is still present: https://www.ecosia.org/search?addon=firefox&q=tor+blog+why+tor+is+slow+site%3Ablog.torproject.org
Though the https://support.torproject.org/tbb/tbb-22/ should contain some more answer to the question in its title..https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40090Add links to all specs available on collector page2023-09-19T09:32:05ZGeorg KoppenAdd links to all specs available on collector pageWhile trying to review collector#40016 I was hunting down references for all the specs involved. It turns out they are all over the place and it's hard to keep track of them. On collector.html we link to some of those specs, which is goo...While trying to review collector#40016 I was hunting down references for all the specs involved. It turns out they are all over the place and it's hard to keep track of them. On collector.html we link to some of those specs, which is good. However, we should collect the links to all the missing specs and add them there, too, so we have at least one canonical place where all specs are just one click away.
Oh, and while we are at it we should replace those old gitweb links.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40089Go over bridge descriptor spec and fix it up where needed2023-06-15T10:29:39ZGeorg KoppenGo over bridge descriptor spec and fix it up where neededWe removed contact information from our sanitization steps a while back in collector#20983 which is not visible on the bridge descriptor [spec](https://metrics.torproject.org/bridge-descriptors.html) yet. We should go over that spec and ...We removed contact information from our sanitization steps a while back in collector#20983 which is not visible on the bridge descriptor [spec](https://metrics.torproject.org/bridge-descriptors.html) yet. We should go over that spec and make sure everything is up-to-date.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/202Get domains for some Onion Service projects2024-03-15T16:32:57ZSilvio RhattoGet domains for some Onion Service projects# Goals
* Get shorter URLs for some Onion Service related projects, pointing to their GitLab Pages.
# Why
* The current URLs are hard to remember and take a lot to type.
# Approaches
## Per-project domains
This approach consists in...# Goals
* Get shorter URLs for some Onion Service related projects, pointing to their GitLab Pages.
# Why
* The current URLs are hard to remember and take a lot to type.
# Approaches
## Per-project domains
This approach consists in having one domain per project:
* [ ] `onionplan.torproject.org` (for [The Onion Plan](https://tpo.pages.torproject.net/onion-services/onionplan/)).
* [ ] `onionbalance.torproject.org` (for [Onionbalance](https://tpo.pages.torproject.net/onion-services/onionbalance/)).
* [ ] `onionprobe.torproject.org` (for [Onionprobe](https://tpo.pages.torproject.net/onion-services/onionprobe/)).
* [ ] `oniongroove.torproject.org` (for [Oniongroove](https://tpo.pages.torproject.net/onion-services/oniongroove/)).
* [ ] `onion-launchpad.torproject.org` (for [Onion Launchpad](https://tpo.pages.torproject.net/onion-services/onion-launchpad/)).
* [ ] `onionspray.torproject.org` (for [Onionspray](https://gitlab.torproject.org/tpo/onion-services/onionspray)) (see [this issue about rebranding the EOTK fork](tpo/onion-services/eotk#13)).
* [ ] `onionmine.torproject.org` (for [Onionmine](https://gitlab.torproject.org/tpo/onion-services/onionmine), check tpo/onion-services/onionmine#26).
Pros:
* Tend to produce shorter URLs.
Cons:
* Involves more work to setup.
## Single Onion Service documentation site
This approach consists in having a single `onionservices.torproject.org` domain, and allocating a subpath for each project:
* [ ] `onionservices.torproject.org/onionplan` (for [The Onion Plan](https://tpo.pages.torproject.net/onion-services/onionplan/)).
* [ ] `onionservices.torproject.org/onionbalance` (for [Onionbalance](https://tpo.pages.torproject.net/onion-services/onionbalance/), check tpo/onion-services/onionbalance#28).
* [ ] `onionservices.torproject.org/onionprobe` (for [Onionprobe](https://tpo.pages.torproject.net/onion-services/onionprobe/)).
* [ ] `onionservices.torproject.org/oniongroove` (for [Oniongroove](https://tpo.pages.torproject.net/onion-services/oniongroove/)).
* [ ] `onionservices.torproject.org/onion-launchpad` (for [Onion Launchpad](https://tpo.pages.torproject.net/onion-services/onion-launchpad/)).
* [ ] `onionservices.torproject.org/onionspray` (for [Onionspray](https://gitlab.torproject.org/tpo/onion-services/onionspray)) (see [this issue about rebranding the EOTK fork](tpo/onion-services/eotk#13)).
* [ ] `onionservices.torproject.org/onionmine` (for [Onionmine](https://gitlab.torproject.org/tpo/onion-services/onionmine), check tpo/onion-services/onionmine#26).
Pros:
* Can be easier for a sysadmin point of view.
* It's self-explanatory.
* May have integrated search across all these projects by leveraging these configurations:
* [mkdocs-multirepo-plugin · PyPI](https://pypi.org/project/mkdocs-multirepo-plugin/)
* [Built-in projects plugin - Material for MkDocs](https://squidfunk.github.io/mkdocs-material/plugins/projects/)
* Could be release as part of the [Onion Services 20th Years Anniversary (2024 edition)](https://gitlab.torproject.org/tpo/onion-services/onionplan/-/issues/14#note_2933136).
Cons:
* May conflict/duplicate efforts with the upcoming [Tor Developer Portal](https://gitlab.torproject.org/groups/tpo/-/milestones/23).
* Requires an additional home page.
## Deployment options
1. Have a static hosting endpoint with changes pushed by GitLab CI jobs, possibly the [static shim][] deploying to the [static component].
2. A reverse proxy setup.
3. Or it may happen that only a redirect/alias is supported (like was done at tpo/tpa/team#40294).
## Bonus
* [ ] Onion Services endpoint and Onion-Location for each site. The Onion Service itself could be one for the entire GitLab pages (and that would also help with tpo/onion-services/onion-launchpad#32, related to tpo/tpa/team#40379).
[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-componentSilvio RhattoSilvio Rhatto2024-02-29https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40088Bridge running flag is determined from bridgestrap tests, not bridge networks...2023-05-04T16:50:26ZGeorg KoppenBridge running flag is determined from bridgestrap tests, not bridge networks statushttps://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/112#note_2857497 claims we get the "running" flag from bridgestrap tests, which seems reasonable given the code linked to. However, the Onionoo documentation on the [Metrics...https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/112#note_2857497 claims we get the "running" flag from bridgestrap tests, which seems reasonable given the code linked to. However, the Onionoo documentation on the [Metrics website](https://metrics.torproject.org/onionoo.html) says: "Boolean field saying whether this bridge was listed as running in the last bridge network status."
It seems we need to change the documentation here.Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/community/policies/-/issues/3Setup GitLab Pages for the Policies repository2023-11-12T17:56:06ZSilvio RhattoSetup GitLab Pages for the Policies repositoryWe could easily convert the text files to markdown and use something like [Onion MkDocs](https://gitlab.torproject.org/rhatto/onion-mkdocs) to render a fancy version of the policies repository.We could easily convert the text files to markdown and use something like [Onion MkDocs](https://gitlab.torproject.org/rhatto/onion-mkdocs) to render a fancy version of the policies repository.GusGushttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41125prepare (and give) training for 2FA with security keys in CR2023-04-27T23:20:17Zanarcatprepare (and give) training for 2FA with security keys in CRIn #41083 we agreed to distribute security keys (specifically Yubikeys) in Costa Rica.
This ticket is to ensure we have a training prepared beforehand and that we give it to people and that people are happy.
We should also, incidentall...In #41083 we agreed to distribute security keys (specifically Yubikeys) in Costa Rica.
This ticket is to ensure we have a training prepared beforehand and that we give it to people and that people are happy.
We should also, incidentally, keep track of the keys to make sure they do end up in CR.
/cc @linus @shelikhooanarcatanarcathttps://gitlab.torproject.org/tpo/web/tpo/-/issues/377document "how to add person to the people's page"2023-05-17T18:28:29Zanarcatdocument "how to add person to the people's page"One of the recurring task when onboarding new people (see also tpo/tpa/team#40129) is "add that user to the people page". This seemingly trivial thing for us is actually quite a challenge for new people.
Let's make a tutorial, step by s...One of the recurring task when onboarding new people (see also tpo/tpa/team#40129) is "add that user to the people page". This seemingly trivial thing for us is actually quite a challenge for new people.
Let's make a tutorial, step by step, with no prior technical knowledge required (other than "I know how to use a web browser", say), on how to do something like this in GitLab.
This will also serve as a good example on the general "how do I change the website" problem.
I'm not sure where this should be documented, but there is already related documentation in the [static shim docs](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/static-shim) (e.g. [Deploying a static site from GitLab CI](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/static-shim#deploying-a-static-site-from-gitlab-ci)) but those (three!) tutorials really are more like How-To, as they assume lots of technical knowledge, and are really more one-time things. So those should be moved out of the tutorial section as well.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org