The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-06-30T17:23:27Zhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40091Document the translation attic2023-06-30T17:23:27ZemmapeelDocument the translation atticWe need to document the translation attic repo: https://gitlab.torproject.org/tpo/community/translation-attic/We need to document the translation attic repo: https://gitlab.torproject.org/tpo/community/translation-attic/emmapeelemmapeelhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40909TPA-RFC-38 wiki replacement2024-03-20T18:27:42ZKezTPA-RFC-38 wiki replacementThis is the discussion ticket for [TPA-RFC-38: Setting Up a Wiki Service](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service). This ticket serves as a place where people can suggest changes to the RFC, ...This is the discussion ticket for [TPA-RFC-38: Setting Up a Wiki Service](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-38-new-wiki-service). This ticket serves as a place where people can suggest changes to the RFC, as well as suggest goals and must-have features for the new wiki serviceanarcatanarcathttps://gitlab.torproject.org/tpo/web/community/-/issues/298[Relays] Document relay setup process for Alpine Linux2023-06-30T00:40:19Zjsw[Relays] Document relay setup process for Alpine Linux### Problem to solve
Alpine Linux limits the number of allowed file descriptors for processes started by open-rc, leading to a `"Failing because we have 4063 connections already..."` warn message.
### Proposal
Documentation should inclu...### Problem to solve
Alpine Linux limits the number of allowed file descriptors for processes started by open-rc, leading to a `"Failing because we have 4063 connections already..."` warn message.
### Proposal
Documentation should include steps to raise this limit by creating an init script containing an `rc_ulimit` directive, and provide more general steps to setup relays on Alpine Linux.
### Who can address the issue
@jswhttps://gitlab.torproject.org/tpo/web/manual/-/issues/130Manual on Bridges speaks of "addresses" but means whole bridge lines2024-01-29T19:32:45ZIan Jacksoniwj@torproject.orgManual on Bridges speaks of "addresses" but means whole bridge linesThe page https://tb-manual.torproject.org/bridges/ speaks of "Bridge addresses" but it means the whole bridge line, including not just the address and port but also PT name, identity key, and PT parameters. I think this is unnecessarily...The page https://tb-manual.torproject.org/bridges/ speaks of "Bridge addresses" but it means the whole bridge line, including not just the address and port but also PT name, identity key, and PT parameters. I think this is unnecessarily confusing.
It might even be leading to users fishing the thing out of the bridge line that looks like an address...
Since internally (and presumably in the community) we speak of "bridge lines", maybe that should be the official terminology? Or we could invent a new term ("bridge spec") maybe, but changing existing usage is slow of course.
We should be clear internally about precisely what the terms mean, and use them consistently (for example, the "bridge line" does not seem to include the `Bridge` that appears as the keyword in torrc).https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41299Add links to the manual in the connection assistant2022-11-30T16:30:48ZPier Angelo VendrameAdd links to the manual in the connection assistantWe may want to add links to the manual in the various error panels on the connection wizard, so that users can get more information there.
/cc @duncanWe may want to add links to the manual in the various error panels on the connection wizard, so that users can get more information there.
/cc @duncanhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41253Include compile instructions in our tor-android-service repo2022-11-29T13:38:38ZGeorg KoppenInclude compile instructions in our tor-android-service repoThe `README.md` file in `tor-android-service` says currently
```
# tor-android-service
Android Service For Intalling and Running Tor
```
. We should be a bit more verbose to help others using this new tool and getting it built outside of...The `README.md` file in `tor-android-service` says currently
```
# tor-android-service
Android Service For Intalling and Running Tor
```
. We should be a bit more verbose to help others using this new tool and getting it built outside of Tor Browser.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41249In tor-android-services, document where the code we imported comes from2022-09-01T23:00:00ZboklmIn tor-android-services, document where the code we imported comes fromIn `tor-android-service`, we have commit tor-android-service@36f9873ff075253f4c1c9e394c91031fd4ba9d4a which is adding a bunch of code:
https://gitweb.torproject.org/tor-android-service.git/commit/?id=36f9873ff075253f4c1c9e394c91031fd4ba9...In `tor-android-service`, we have commit tor-android-service@36f9873ff075253f4c1c9e394c91031fd4ba9d4a which is adding a bunch of code:
https://gitweb.torproject.org/tor-android-service.git/commit/?id=36f9873ff075253f4c1c9e394c91031fd4ba9d4a
However it seems that this code has been taken from various other places, but there is no indication of where.
Ideally we would have kept history of the projects we imported code from (for example with `git filter-branch`), or just used sub-modules if we did not modify them. But since we didn't do that, I think we should at least put somewhere the information about where all the code we include comes from.
For example the `jsocksAndroid` directory seems to be imported from https://github.com/guardianproject/jsocks or maybe https://github.com/ravn/jsocks, but there is no indication of that, or which commit was used. The directory `service/` looks similar to https://github.com/guardianproject/orbot/tree/master/orbotservice, but there is no indication that it was imported from there, or which commit was used.
I am also wondering why we have both `jsocksAndroid/` and `external/jsocks/`.
We also have a `LICENSE` file containing the Apache License, but it is unclear to what it applies since this is neither the license of Orbot of jsocks.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41189Automate and document local dev build for Fenix2022-11-29T12:36:57ZaguestuserAutomate and document local dev build for Fenix# Context
- currently, the only documented way to build tbb-android is through torbrowser-build, which works but takes several hours for a clean build
- we would like to be able to run a quicker build to iterate on code changes in androi...# Context
- currently, the only documented way to build tbb-android is through torbrowser-build, which works but takes several hours for a clean build
- we would like to be able to run a quicker build to iterate on code changes in android studio, but this is hard b/c we need to inject artifacts for all of our patched layers (`tor-android-service`, `tor-onion-proxy-library`, `android-components`, and `geckoview`) into the gradle cache in order for the build to run correctly
- SO: here we will (1) write down all the steps necessary to perform such injections, (2) script them to the extent possible to make it easier to update injected artifacts as patches to underlying layers are updatedDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/web/community/-/issues/293[Training] Consider merging 'Best Practices' and the checklist sections2023-05-11T18:29:50Zemmapeel[Training] Consider merging 'Best Practices' and the checklist sectionsThe [best practices](https://community.torproject.org/training/best-practices/) and the [checklist](https://community.torproject.org/training/checklist/) training sections have both similar content.
Maybe we should merge them, especiall...The [best practices](https://community.torproject.org/training/best-practices/) and the [checklist](https://community.torproject.org/training/checklist/) training sections have both similar content.
Maybe we should merge them, especially the parts of 'best practices' that have a checklist format for before and after the training.
Working pad: https://pad.riseup.net/p/tor-merge-best-practices-checklistrayarayahttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40082Document possibility of submitting merge requests to the translation repo, in...2023-09-27T15:23:23ZemmapeelDocument possibility of submitting merge requests to the translation repo, instead of using a translation platformIt is possible to update the translation files through git, and then using the tx client push function in transifex. in weblate it will be even easier.
But it is not documented.
So, we should document a way for contributors to contribu...It is possible to update the translation files through git, and then using the tx client push function in transifex. in weblate it will be even easier.
But it is not documented.
So, we should document a way for contributors to contribute like this.
This will also be beneficial for example if we need to change a term in many places at once.emmapeelemmapeelhttps://gitlab.torproject.org/tpo/web/community/-/issues/286Move bridge post-install info to "Technical Setup"2023-01-11T16:38:28ZGhost UserMove bridge post-install info to "Technical Setup"<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
<!-- Use this section to explain the proposal and how it will work. It can be helpful to add technical detai...<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
<!-- Use this section to explain the proposal and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
The relay post-install info is located at [/relay/setup/post-install/](https://community.torproject.org/relay/setup/post-install/), but the bridge post-install info is mixed in between the operating systems at [/relay/setup/bridge/post-install/](https://community.torproject.org/relay/setup/bridge/post-install/).
I suggest moving the bridge post-install page next to the relay post-install page at [/relay/setup/](https://community.torproject.org/relay/setup/).
What needs to be done:
- Move /relay/setup/post-install/ to /relay/setup/relay-post-install/
- Move /relay/setup/bridge/post-install/ to /relay/setup/bridge-post-install/
- Update all links to the new destination of /relay/setup/post-install/
- Update all links to the new destination of /relay/setup/bridge/post-install/
- Change the title of /relay/setup/bridge-post-install/contents.lr to "Bridge Post-install"
- Change the key of /relay/setup/bridge-post-install/contents.lr to "4"
- Change the key of /relay/setup/post-install/contents.lr from "4" to "5"
- Change the key of /relay/setup/snowflake/contents.lr from "5" to "6"
I could work on this.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40578Add README to Tor Browser2023-01-05T14:22:24ZtraumschuleAdd README to Tor BrowserI am struck that there is none.
```
tor-browser8.5a1$ find |grep -i readme
./Browser/TorBrowser/Docs/Obfsproxy/README
./Browser/TorBrowser/Docs/fteproxy/README.md
./Browser/TorBrowser/Docs/meek/README
./Browser/TorBrowser/Docs/libfte/RE...I am struck that there is none.
```
tor-browser8.5a1$ find |grep -i readme
./Browser/TorBrowser/Docs/Obfsproxy/README
./Browser/TorBrowser/Docs/fteproxy/README.md
./Browser/TorBrowser/Docs/meek/README
./Browser/TorBrowser/Docs/libfte/README.md
./Browser/TorBrowser/Docs/snowflake/README.md
```https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40559Add Tor Browser-specific licenses in about:license2023-01-05T13:54:25ZMatthew FinkelAdd Tor Browser-specific licenses in about:licenseThis idea came out of legacy/trac#33771 and legacy/trac#33772. GeKo mentioned that we don't need to ship a specific license for NSS because it is covered by `about:license`, and we could use `about:license` for the additional licenses we...This idea came out of legacy/trac#33771 and legacy/trac#33772. GeKo mentioned that we don't need to ship a specific license for NSS because it is covered by `about:license`, and we could use `about:license` for the additional licenses we must ship, as well. Currently those Tor Browser-specific licenses are controlled by tor-browser-build and they are included as text files at build-time. Extending `about:license` is a good idea.
The main disadvantage I see is downstream projects who take a tor browser package and re-use all of the tor parts but they don't use the browser. We could achieve this by continuing with adding licenses in text files and then patching them into tor-browser's `toolkit/content/license.html` at build time. I'm not very excited about the additional complexity this would require, though.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40556Show the Tor Browser version number on f-droid (instead of firefox version)2022-08-02T12:17:24ZboklmShow the Tor Browser version number on f-droid (instead of firefox version)It seems that some users are confused by the version number that is shown on f-droid:
https://blog.torproject.org/comment/285989#comment-285989
It looks like the version number that is shown is the Firefox version on which it is based, ...It seems that some users are confused by the version number that is shown on f-droid:
https://blog.torproject.org/comment/285989#comment-285989
It looks like the version number that is shown is the Firefox version on which it is based, instead of the Tor Browser version.https://gitlab.torproject.org/tpo/web/support/-/issues/307Add MetricsPort to the glossary2022-07-27T19:14:56ZemmapeelAdd MetricsPort to the glossaryWe should add to the glossary some more terms, and translator dfiguera has found MetricsPort.
Maybe there are more.We should add to the glossary some more terms, and translator dfiguera has found MetricsPort.
Maybe there are more.https://gitlab.torproject.org/tpo/web/community/-/issues/281Onion-Location documentation is a bit confusing and hard to translate2023-08-02T05:17:59ZemmapeelOnion-Location documentation is a bit confusing and hard to translatereporter by translator, confirmed by me.
The documentation about Onion-Location https://community.torproject.org/onion-services/advanced/onion-location/ is a bit confusing.
It seems different documentations have been merged on the page...reporter by translator, confirmed by me.
The documentation about Onion-Location https://community.torproject.org/onion-services/advanced/onion-location/ is a bit confusing.
It seems different documentations have been merged on the page, and the examples change names along the differect sections.
For example the onion address is called: `<your-onion-address>.onion`, http://{$TOR_HOSTNAME}, <your-onion-service-address.onion>, etc.
There are also some 'fake' paths in the style of `"/path/to/www.example.com.cert"` that are difficult to translate, particularly for LTR or different character languages.
Maybe it is better to start the page with some example URL and onion address and use them along the different configuration and commands of the howto.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40543Move reproducible builds documentation into a modularized world2022-12-22T15:49:06ZGeorg KoppenMove reproducible builds documentation into a modularized worldFor lack of a better component I am filing a ticket here for now: where do we document the whole new setup now that tor-browser-build becomes just a project among others? There will be tor-browser-build related documentation changes, sur...For lack of a better component I am filing a ticket here for now: where do we document the whole new setup now that tor-browser-build becomes just a project among others? There will be tor-browser-build related documentation changes, sure. But we'd benefit from a general outline for someone who wanted to get started and use rbm for their project in a modularized world. While I like the idea of having "Reproducible builds at Tor", say, on a wiki page in /applications/team it might not be the right place for that general part.https://gitlab.torproject.org/tpo/applications/team/-/issues/11Update QA and Testing content on our HACKING document2022-06-23T22:20:56ZGeorg KoppenUpdate QA and Testing content on our HACKING documentOur QA and Testing content on our HACKING page needs some update.Our QA and Testing content on our HACKING page needs some update.https://gitlab.torproject.org/tpo/web/support/-/issues/305Onion Services glossary entry misses features2023-01-18T18:33:19ZemmapeelOnion Services glossary entry misses featuresIt seems the list of advantages of Onion Services over ordinary services on the non-private web got lost at some point in the Glossary, as the text ends like this:
`Onion services offer advantages over ordinary services on the non-priva...It seems the list of advantages of Onion Services over ordinary services on the non-private web got lost at some point in the Glossary, as the text ends like this:
`Onion services offer advantages over ordinary services on the non-private web, including:`
We should add the advantages back, maybe recovering them from the trac glossary.
Ref> https://support.torproject.org/glossary/onion-services/
Reported by translator Kate_, thanks!https://gitlab.torproject.org/tpo/core/arti/-/issues/508gitlab-pages is easy to forget to update, and interacts badly with coverage2022-12-13T20:44:03Ztrinity-1686agitlab-pages is easy to forget to update, and interacts badly with coveragethe [gitlab pages](https://tpo.pages.torproject.net/core/arti/) for Arti says it's still 0.3, but 0.4 is available.
Updating the `pages` branch would cause coverage report to disappear (and reappear on next scheduled CI job). I think t...the [gitlab pages](https://tpo.pages.torproject.net/core/arti/) for Arti says it's still 0.3, but 0.4 is available.
Updating the `pages` branch would cause coverage report to disappear (and reappear on next scheduled CI job). I think this branch should not exist, and the website should be directly on `main`. This would make the release process easier (only one branch to update), and would make the CI less strange in how deploying pages is done.