The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2023-02-23T12:25:34Zhttps://gitlab.torproject.org/tpo/web/manual/-/issues/139Remove upload bug on Tor Browser for Android from Known issues2023-02-23T12:25:34Zchampionquizzerchampionquizzer@torproject.orgRemove upload bug on Tor Browser for Android from Known issuesAs https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40283 is now fixed, we should remove it from the 'Known issues' section in Mobile Tor: https://tb-manual.torproject.org/mobile-tor/#known-issuesAs https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40283 is now fixed, we should remove it from the 'Known issues' section in Mobile Tor: https://tb-manual.torproject.org/mobile-tor/#known-issueschampionquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/network-health/tor-weather/-/issues/19Explain requirements for variables in settings.py2023-02-02T04:39:52ZGeorg KoppenExplain requirements for variables in settings.pyWe have some variables needed in src/settings.py that are pretty straightforward to deal with (like `SMTP_PORT`) but others need some comment/explanation so folks know what they are supposed to so. Two examples that come to mind right no...We have some variables needed in src/settings.py that are pretty straightforward to deal with (like `SMTP_PORT`) but others need some comment/explanation so folks know what they are supposed to so. Two examples that come to mind right now:
1. We should mention that the onionoo job interval specified is in *minutes*.
2. We should give some hint as to whether there are some needs for the `JWT_SECRET`. Could it just be "test1234" or some other text or does it need to be formatted particularly or...?
Apart from those two we might want to think whether other variables would benefit from a comment having in mind someone needing to set this app up who might not know all of the nitty-gritty details involved in it.https://gitlab.torproject.org/tpo/network-health/onbasca/-/issues/134Add documentation on how to build documentation, run tests and add example co...2023-12-11T09:55:56ZjugaAdd documentation on how to build documentation, run tests and add example configurationsjugajugahttps://gitlab.torproject.org/tpo/web/manual/-/issues/138Update GetTor instructions2023-01-12T21:01:16Zchampionquizzerchampionquizzer@torproject.orgUpdate GetTor instructionsSince Tor Browser 12 we have single multi-locale builds and users, while downloading from the GetTor service either via email or Telegram distributors, don't need to specify the locale. The instructions on https://tb-manual.torproject.or...Since Tor Browser 12 we have single multi-locale builds and users, while downloading from the GetTor service either via email or Telegram distributors, don't need to specify the locale. The instructions on https://tb-manual.torproject.org/downloading/ should reflect this update.championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/core/torspec/-/issues/176Make human summary of Tor Browser design doc2023-01-09T17:43:33ZMike PerryMake human summary of Tor Browser design docWe should create a brief human-readable summary of the privacy properties of TBB, based on the Design Requirements.
We should probably include this in the short user manual, or on the download page, or both.
See also https://lists.torp...We should create a brief human-readable summary of the privacy properties of TBB, based on the Design Requirements.
We should probably include this in the short user manual, or on the download page, or both.
See also https://lists.torproject.org/pipermail/tor-talk/2012-January/022899.html.https://gitlab.torproject.org/tpo/applications/team/-/issues/18Document auditing setups for testers to use2023-01-05T18:15:17ZMike PerryDocument auditing setups for testers to useWe've got a TBB AppArmor profile at https://trac.torproject.org/projects/tor/wiki/doc/AppArmorForTBB. On legacy/trac#5741, some dude named unknown posted iptables rules that log violations. I hear there is also an OSX Seatbelt policy flo...We've got a TBB AppArmor profile at https://trac.torproject.org/projects/tor/wiki/doc/AppArmorForTBB. On legacy/trac#5741, some dude named unknown posted iptables rules that log violations. I hear there is also an OSX Seatbelt policy floating around somewhere that may also be useful.
We should create a meta document, or perhaps just describe on https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff how to use these things to test for disk leaks, proxy issues, oddities, and other violations.https://gitlab.torproject.org/tpo/applications/team/-/issues/17Make human summary of Tor Browser design doc2023-01-09T00:15:50ZMike PerryMake human summary of Tor Browser design docWe should create a brief human-readable summary of the privacy properties of TBB, based on the Design Requirements.
We should probably include this in the short user manual, or on the download page, or both.
See also https://lists.torp...We should create a brief human-readable summary of the privacy properties of TBB, based on the Design Requirements.
We should probably include this in the short user manual, or on the download page, or both.
See also https://lists.torproject.org/pipermail/tor-talk/2012-January/022899.html.https://gitlab.torproject.org/tpo/applications/team/-/issues/16Create Style Guides2023-01-05T18:14:59ZMatthew FinkelCreate Style GuidesFollowing legacy/trac#26184, we should document our coding style preferences. We should consider documenting all Tor Browser-related projects.Following legacy/trac#26184, we should document our coding style preferences. We should consider documenting all Tor Browser-related projects.Sponsor 131 - Phase 5 - Ongoing Maintenancehttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40107Broken link in the Wiki2023-02-02T15:31:30ZDavid Figueradfb@mm.stBroken link in the WikiAt https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-reviewers there's a link to https://tpo.pages.torproject.net/community/l10n/ which results in NXDOMAIN in DNS.At https://gitlab.torproject.org/tpo/community/l10n/-/wikis/Localization-for-reviewers there's a link to https://tpo.pages.torproject.net/community/l10n/ which results in NXDOMAIN in DNS.emmapeelemmapeelhttps://gitlab.torproject.org/tpo/core/arti/-/issues/706Missing documentation concerning Bridge and PT configuration.2023-07-03T21:56:53ZNick MathewsonMissing documentation concerning Bridge and PT configuration.`hackerencoder` on IRC spotted these issues:
* The `transports()` method in `BridgesConfig` does not appear in our documentation: https://tpo.pages.torproject.net/core/doc/rust/arti_client/config/struct.BridgesConfig.html
* `BridgeCon...`hackerencoder` on IRC spotted these issues:
* The `transports()` method in `BridgesConfig` does not appear in our documentation: https://tpo.pages.torproject.net/core/doc/rust/arti_client/config/struct.BridgesConfig.html
* `BridgeConfigBuilder`'s documentation doesn't explain itself very well if you don't already know the terminology (What is a direct connection? What is "k"? What is "v"? What is a setting?)
We fix these issues, then we should read over our generated documentation to make sure that it's clear to somebody who doesn't already know how to configure bridges and PTs.Arti 1.1.0: Anticensorship readyNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40077Document how to reproduce the "Total consensus weights across bandwidth autho...2022-12-14T13:57:05ZGeorg KoppenDocument how to reproduce the "Total consensus weights across bandwidth authorities"-graphOn https://metrics.torproject.org/totalcw.html we link to https://metrics.torproject.org/reproducible-metrics.html#servers for steps on how to reproduce the graph. However, https://metrics.torproject.org/reproducible-metrics.html#servers...On https://metrics.torproject.org/totalcw.html we link to https://metrics.torproject.org/reproducible-metrics.html#servers for steps on how to reproduce the graph. However, https://metrics.torproject.org/reproducible-metrics.html#servers is missing a section documenting the respective steps.https://gitlab.torproject.org/tpo/onion-services/onion-launchpad/-/issues/72Documentation2024-02-26T17:25:15ZSilvio RhattoDocumentation* [x] Setup documentation with [onion-mkdocs]() and GitLab pages withing a subfolder (like `docs/`), since the GitLab pages space is already allocated by the main code.
* [x] Move some [README.md](README.md) content into multiple files i...* [x] Setup documentation with [onion-mkdocs]() and GitLab pages withing a subfolder (like `docs/`), since the GitLab pages space is already allocated by the main code.
* [x] Move some [README.md](README.md) content into multiple files inside a `docs/` folder.Silvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40711Review and expand the stakeholders we communicate major changes to2022-12-19T18:48:16ZdonutsReview and expand the stakeholders we communicate major changes to@richard has created this checklist as part of the release process (which is awesome):
```
### notify stakeholders
* [ ] Email tor-qa mailing list: [tor-qa@lists.torproject.org](mailto:tor-qa@lists.torproject.org)
* [ ] Provide links...@richard has created this checklist as part of the release process (which is awesome):
```
### notify stakeholders
* [ ] Email tor-qa mailing list: [tor-qa@lists.torproject.org](mailto:tor-qa@lists.torproject.org)
* [ ] Provide links to unsigned builds on `$(BUILD_SERVER)`
* [ ] Call out any new functionality which needs testing
* [ ] Link to any known issues
* [ ] Email Tails dev mailing list: [tails-dev@boum.org](mailto:tails-dev@boum.org)
* [ ] Provide links to unsigned builds on `$(BUILD_SERVER)`
```
And also:
```
### tor-announce mailing list
* [ ] Send an email to [tor-announce@lists.torproject.org](mailto:tor-announce@lists.torproject.org), using the same content as the blog post and subject "Tor Browser $version is released".
```
However it looks like we caught torbrowser-launcher unawares with the 12.0 release: https://github.com/micahflee/torbrowser-launcher/issues/659
We should take the opportunity to review how we notify external stakeholders during development, and expand this list to include Micah Lee & The Guardian Project at minimum (who don't necessarily have the time to read every tor-qa or tor-announce email).richardrichardhttps://gitlab.torproject.org/tpo/applications/team/-/issues/15Review and expand the stakeholders we communicate major changes to2022-12-09T16:55:11ZdonutsReview and expand the stakeholders we communicate major changes to@richard has created this checklist as part of the release process (which is awesome):
```
### notify stakeholders
* [ ] Email tor-qa mailing list: [tor-qa@lists.torproject.org](mailto:tor-qa@lists.torproject.org)
* [ ] Provide links...@richard has created this checklist as part of the release process (which is awesome):
```
### notify stakeholders
* [ ] Email tor-qa mailing list: [tor-qa@lists.torproject.org](mailto:tor-qa@lists.torproject.org)
* [ ] Provide links to unsigned builds on `$(BUILD_SERVER)`
* [ ] Call out any new functionality which needs testing
* [ ] Link to any known issues
* [ ] Email Tails dev mailing list: [tails-dev@boum.org](mailto:tails-dev@boum.org)
* [ ] Provide links to unsigned builds on `$(BUILD_SERVER)`
```
And also:
```
### tor-announce mailing list
* [ ] Send an email to [tor-announce@lists.torproject.org](mailto:tor-announce@lists.torproject.org), using the same content as the blog post and subject "Tor Browser $version is released".
```
However it looks like we caught torbrowser-launcher unawares with the 12.0 release: https://github.com/micahflee/torbrowser-launcher/issues/659
We should take the opportunity to review how we notify external stakeholders during development, and expand this list to include Micah Lee & The Guardian Project at minimum (who don't necessarily have the time to read every tor-qa or tor-announce email).https://gitlab.torproject.org/tpo/tpa/team/-/issues/40999followup on TPA-RFC-27: Python 2 removal in bookworm2023-07-05T14:42:44Zanarcatfollowup on TPA-RFC-27: Python 2 removal in bookwormin #33949, we decided to EOL Python 2 inside TPA. The actual [proposal](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-27-python2-eol) [timeline](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-27-pyt...in #33949, we decided to EOL Python 2 inside TPA. The actual [proposal](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-27-python2-eol) [timeline](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-27-python2-eol#timeline) said:
> Debian 12 bookworm upgrades are currently scheduled to begin some time in 2023 and should be completed before July 2024. An actual schedule will be proposed in a future announcement. When this change will be deployed, Python 2 will be gone from TPA servers.
This ticket is to followup on that step, when we upgrade all servers to bookworm and Python 2 is definitely removed from our servers. It's possible (though unlikely) that some Python 2 programs remain on the upgraded bullseye servers, so this ticket will make sure we make proper announcements and porting if we encounter those.Debian 12 bookworm upgradeanarcatanarcathttps://gitlab.torproject.org/tpo/web/donate-static/-/issues/98Donor FAQ bugs/suggestions RE: bank transfer2023-08-24T04:26:31ZmattlavDonor FAQ bugs/suggestions RE: bank transferFrom [this ticket](https://rt.torproject.org/Ticket/Display.html?id=270570):
===========================================
Dear torproject team,
I want to donate using eu bank transfer. I looked at your FAQ and found
some "bugs" that m...From [this ticket](https://rt.torproject.org/Ticket/Display.html?id=270570):
===========================================
Dear torproject team,
I want to donate using eu bank transfer. I looked at your FAQ and found
some "bugs" that make this harder. Therefore I want to suggest some
improvements to the faq, to make donating easier. I hope this way you
might get more donations to make tor even better.
TLDR: Proposals:
1) Fix the link "EU Bank Transfer" in
https://donate.torproject.org/donor-faq section 3 so that it points the
user to the IBAN directly
2) Add clearer wording that the listed IBAN is the one to use for donations.
3) Besides the IBAN tell the donors which reference to use in the bank
transfer (or make clear that the reference does not matter if none is
needed)
Details: Motivation/My experience with the faq site:
I visited your donation side https://donate.torproject.org because I wanted to donate with eu bank transfer. I found your faq and the section "3. How else can I donate to the Tor Project?". But clicking in "EU Bank Transfer" only brings me to the top of the page. (The link is https://donate.torproject.org/donor-faq/#eu-bank-transfer, the anchor seems to be broken).
So it is quite hard to find the correct way to donate. After reading the whole faq I found section "15. Is my donation tax-deductible?" which mentions the Renewable Freedom Foundation and a IBAN. But the wording is not really clear: It talks about tax-deductible donations, but does not say "this is the IBAN to use for donations to us". Additionally it confused me that there is no Reference given that should be used, like "donation torproject", which I would expect here to be needed so the Renewable Freedom Foundation can find out to whom I want to donate.
===========================================
Assigning this to @smith for now; as mentioned in the ticket, these suggestions are probably wise to implement now, and also to keep in mind as we establish Open Collective as our fiscal sponsor in Europe.al smithal smithhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40979document our fastly/CDN setup2022-11-30T19:55:45Zanarcatdocument our fastly/CDN setupso we have a CDN we use here, and it's not really documented. we have fairly good docs on the ~"static-component" system, but nothing on ~Fastly. we didn't even have a tag for it until #40978 was filed (and i made it).
so we should docu...so we have a CDN we use here, and it's not really documented. we have fairly good docs on the ~"static-component" system, but nothing on ~Fastly. we didn't even have a tag for it until #40978 was filed (and i made it).
so we should document:
* [ ] what we use fastly for
* [ ] how it's configured (e.g. `cdn-config-fastly.git`, `./tor-puppet/modules/roles/files/puppetmaster/update-fastly-ips`, static-component yaml file, probably more)
* [ ] what talks to it and why not everything is on there
* [ ] what our limits are
* [ ] contact information
* [ ] password management
basically make a full service audit.anarcatanarcathttps://gitlab.torproject.org/tpo/core/arti/-/issues/624Document (somewhere) how all of high-level objects fit together, esp wrt Weak2023-01-06T19:17:30ZNick MathewsonDocument (somewhere) how all of high-level objects fit together, esp wrt WeakThis comes out of a discussion at https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/832#note_2851907.
We should have an architectural document that explains how a `TorClient`'s constituent parts, and the async tasks that make...This comes out of a discussion at https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/832#note_2851907.
We should have an architectural document that explains how a `TorClient`'s constituent parts, and the async tasks that make them run, are all fit together. We should explain why all of our Weak references are that way.Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40937CI for wiki-replica is broken2022-10-24T20:11:50ZJérôme Charaouilavamind@torproject.orgCI for wiki-replica is brokenSince the markdownlint project on GitHub has [updated](https://github.com/markdownlint/markdownlint/commit/865ab4408132de980baddb9448047f411f4e3325) their docker image a week ago, the [wiki-replica CI](https://gitlab.torproject.org/tpo/t...Since the markdownlint project on GitHub has [updated](https://github.com/markdownlint/markdownlint/commit/865ab4408132de980baddb9448047f411f4e3325) their docker image a week ago, the [wiki-replica CI](https://gitlab.torproject.org/tpo/tpa/wiki-replica/-/jobs) is unable to run any tests because the container bootstrap is failing with:
> ERROR: Job failed (system failure): Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown (exec.go:78:0s)anarcatanarcathttps://gitlab.torproject.org/tpo/web/team/-/issues/44Archive and redirect gettor.torproject.org landing page to support portal2024-01-11T13:54:11ZGusArchive and redirect gettor.torproject.org landing page to support portalAlthough GetTor service is very important and useful for users where torproject.org website is blocked, I don't get what's the point of having GetTor landing page since all the instructions are available on Support portal and on Tor Brow...Although GetTor service is very important and useful for users where torproject.org website is blocked, I don't get what's the point of having GetTor landing page since all the instructions are available on Support portal and on Tor Browser Manual, which is bundled in TB.
So, here is my proposal to archive and redirect gettor.torproject.org:
- Improve gettor entry on https://support.torproject.org/censorship
- Archive the repository: https://gitlab.torproject.org/tpo/web/gettor-web
- Redirect gettor.torproject.org to support.torproject.org/censorship
- Remove gettor-web from weblateSponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibetemmapeelemmapeel