The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2022-09-01T23:00:00Zhttps://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/anti-censorship/pluggable-transports/conjure/-/issues/20Building instructions2023-01-27T01:33:24ZVortBuilding instructionsFrom forum post:
"_Instructions for cloning and building this PT are in the repository[4]_"
https://forum.torproject.net/t/tor-dev-introducing-a-conjure-pt-for-tor/4429
However, I can't find build instructions here.
I was able to...From forum post:
"_Instructions for cloning and building this PT are in the repository[4]_"
https://forum.torproject.net/t/tor-dev-introducing-a-conjure-pt-for-tor/4429
However, I can't find build instructions here.
I was able to figure out how to build it, but it is better to have instructions.Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40614Update release templates with feedback from ma12022-08-30T17:41:11ZrichardUpdate release templates with feedback from ma1@ma1 went through the release prep process for 11.5.3 and had some feedback. We should update the templates to be more clear and make explicit the implicit.@ma1 went through the release prep process for 11.5.3 and had some feedback. We should update the templates to be more clear and make explicit the implicit.richardrichardhttps://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/applications/tor-browser-build/-/issues/40612Migrate Release Prep template to Release Prep - Stable2022-08-19T17:46:24ZrichardMigrate Release Prep template to Release Prep - StableAfter #40607 is merged we should update the existing template and migrate it to `Release Prep - Stable` and purge the various 'if stable vs if alpha' logic from it.After #40607 is merged we should update the existing template and migrate it to `Release Prep - Stable` and purge the various 'if stable vs if alpha' logic from it.richardrichardhttps://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/128Broken link on help page2022-08-30T21:03:58ZStefani BanerianBroken link on help pagepage
https://gitlab.torproject.org/help/gitlab-basics/start-using-git#merge-a-branch-with-default-branch
has a broken link, right under the code section.
https://gitlab.torproject.org/help/user/project/merge_requests/ gives a '404'page
https://gitlab.torproject.org/help/gitlab-basics/start-using-git#merge-a-branch-with-default-branch
has a broken link, right under the code section.
https://gitlab.torproject.org/help/user/project/merge_requests/ gives a '404'anarcatanarcathttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40607Add alpha-specific release prep template2022-08-19T17:50:09ZrichardAdd alpha-specific release prep templateThings are changing a fair bit between stable and alpha in terms of the release process given the transition to ESR for android, pending unification of tor-browser and geckoview, etc so we will make a new `Release Prep - Alpha` template ...Things are changing a fair bit between stable and alpha in terms of the release process given the transition to ESR for android, pending unification of tor-browser and geckoview, etc so we will make a new `Release Prep - Alpha` template for these releases, and rename the existing one to `Release Prep - Stable`richardrichardhttps://gitlab.torproject.org/tpo/web/community/-/issues/292Add missing links to the Legal FAQ2023-11-08T23:21:30ZemmapeelAdd missing links to the Legal FAQReported by translator Kate, confirmed by me.
On the [Tor Legal FAQ](https://community.torproject.org/relay/community-resources/eff-tor-legal-faq/) contributed by the EFF we say:
> If you do decide to run an exit relay from your home d...Reported by translator Kate, confirmed by me.
On the [Tor Legal FAQ](https://community.torproject.org/relay/community-resources/eff-tor-legal-faq/) contributed by the EFF we say:
> If you do decide to run an exit relay from your home despite these risks, please review Tor’s recommendations, including telling your ISP and obtaining a separate IP address for the exit relay.
t would be better if "Tor’s recommendations" is a link to our recommendations.https://gitlab.torproject.org/tpo/web/manual/-/issues/129Add @getbridgesbot instructions2022-10-06T14:13:46ZGusAdd @getbridgesbot instructions
Update this page: https://tb-manual.torproject.org/bridges/
And add:
Sending "/bridges" to the dedicated Telegram channel @GetBridgesBot and then adding the bridge address received manually via copy and paste in Tor Browser: Settings ...
Update this page: https://tb-manual.torproject.org/bridges/
And add:
Sending "/bridges" to the dedicated Telegram channel @GetBridgesBot and then adding the bridge address received manually via copy and paste in Tor Browser: Settings > Connection > Bridges > Enter a bridge address you already knowchampionquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/network-health/team/-/issues/254Document metrics dashboards in our wiki2022-09-27T14:23:09ZGeorg KoppenDocument metrics dashboards in our wikiThanks mostly to @hiro's work we have a bunch of dashboards with useful data now. However, given that a lot of them have grown out of experimentation with the tooling and data there is a certain amount of "mushrooming" visible, which mak...Thanks mostly to @hiro's work we have a bunch of dashboards with useful data now. However, given that a lot of them have grown out of experimentation with the tooling and data there is a certain amount of "mushrooming" visible, which makes it hard to keep track of the important and useful dashboards. (Right now, I am fighting with a bunch of bookmarks in my browser for that, often forgetting where and whether we have data X visualized)
We should create something like metrics/dashboards in our wiki where we list our useful (could be experimental as well!) dashboards, explaining what they provide with links to them and to the scripts "sustaining" those dashboards.HiroHirohttps://gitlab.torproject.org/tpo/web/tpo/-/issues/320download page contains outdated information about https-everywhere2022-08-12T22:28:01Ztrinity-1686adownload page contains outdated information about https-everywherehttps://www.torproject.org/download/ says
> Tor Browser already comes with HTTPS Everywhere
This is no longer true since the release of [Tor Browser 11.5](https://blog.torproject.org/new-release-tor-browser-115/), where it was replaced...https://www.torproject.org/download/ says
> Tor Browser already comes with HTTPS Everywhere
This is no longer true since the release of [Tor Browser 11.5](https://blog.torproject.org/new-release-tor-browser-115/), where it was replaced by Firefox "HTTPS-Only" modeGusGushttps://gitlab.torproject.org/tpo/core/arti/-/issues/531tor-proto: Add a head comment explaining the conceptual division between tor-...2022-08-11T13:50:13ZNick Mathewsontor-proto: Add a head comment explaining the conceptual division between tor-proto and higher layersThe `tor-proto` crate should explain that `tor-proto` is a function-only implementation of pieces of the Tor protocols: it does not understand what circuits and channels are getting used for, only _how they should behave_.
This distinct...The `tor-proto` crate should explain that `tor-proto` is a function-only implementation of pieces of the Tor protocols: it does not understand what circuits and channels are getting used for, only _how they should behave_.
This distinction is important to avoid the antipattern where we get single flags (e.g. "This is an exit circuit") that have a complicated set of consequences (e.g. "Exit-ness influences the padding times, the queue timeouts, the cell scheduling priority, . All of those modules work by inspecting the exit-ness flag.") We're trying to prevent this antipattern by making it so the non-behavioral information is kept out of the code that implements the behavior.
So I should document that.Nick MathewsonNick Mathewsonhttps://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/308[Apt] Update instructions on "Can I use APT over Tor?"2022-07-26T19:34:25ZGus[Apt] Update instructions on "Can I use APT over Tor?"- [x] tor nightly repository was renamed to `tor-nightly-main-<distribution>`
- [x] Fix the instructions GPG key instruction- [x] tor nightly repository was renamed to `tor-nightly-main-<distribution>`
- [x] Fix the instructions GPG key instructionGusGushttps://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.