The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2024-03-14T13:34:43Zhttps://gitlab.torproject.org/tpo/community/l10n/-/issues/40131Add more screenshots for the Tor Browser translations2024-03-14T13:34:43ZemmapeelAdd more screenshots for the Tor Browser translationsThe browser strings need more context for a good translation, especially the ones with variables that make translators confused.
At the moment the Tor Browser strings without screenshots can be listed here: https://hosted.weblate.org/se...The browser strings need more context for a good translation, especially the ones with variables that make translators confused.
At the moment the Tor Browser strings without screenshots can be listed here: https://hosted.weblate.org/search/tor/tor-browser/?q=+language%3Aen+and+NOT+has%3Ascreenshot+and+not+component%3Ator-browser-user-manual&sort_by=-priority%2Cposition&checksum=emmapeelemmapeelhttps://gitlab.torproject.org/tpo/community/training/-/issues/141[Privacy Resilience Grants] Record and upload trainings for incoming Tor trai...2024-03-06T13:44:06Zraya[Privacy Resilience Grants] Record and upload trainings for incoming Tor trainerscc: @guscc: @gusrayarayahttps://gitlab.torproject.org/tpo/network-health/metrics/tor_fusion/-/issues/3Make tor_fusion deployment on metricsdb-01 and add documentation to the readme2024-03-05T15:10:35ZHiroMake tor_fusion deployment on metricsdb-01 and add documentation to the readmeTime has come to make a tor_fusion deployment on metricsdb-01 to parse onionperf files. We should also document how the deployment process works and how the service can be maintained.Time has come to make a tor_fusion deployment on metricsdb-01 to parse onionperf files. We should also document how the deployment process works and how the service can be maintained.HiroHirohttps://gitlab.torproject.org/tpo/network-health/metrics/networkstatusapi/-/issues/50Open up Victoria Metrics query engine to the public2024-03-18T16:45:20ZHiroOpen up Victoria Metrics query engine to the public@mattrighetti has been wondering if VictoriaMetrics (VM for short) can be opened to the public so the API doesn't have to proxy requests to the DB but can just pass a 302 code and clients can query VM directly.
I personally have a conce...@mattrighetti has been wondering if VictoriaMetrics (VM for short) can be opened to the public so the API doesn't have to proxy requests to the DB but can just pass a 302 code and clients can query VM directly.
I personally have a concern that services will abuse the VM search engine and crash our service, and I am wondering what we could do to prevent this. I am specifically wondering if is there some token system where only authorized clients could query VM.Mattia RighettiMattia Righettihttps://gitlab.torproject.org/tpo/web/tpo/-/issues/410Design mockups of the new download page on mobile2024-03-19T00:07:22ZdonutsDesign mockups of the new download page on mobileDesktop designs here: [Figma link](https://www.figma.com/file/nIpahk0b9VMaeEnubiO33g/Marble?type=design&node-id=679%3A10&mode=design&t=cHkDPRyD6oerlgAW-1)Desktop designs here: [Figma link](https://www.figma.com/file/nIpahk0b9VMaeEnubiO33g/Marble?type=design&node-id=679%3A10&mode=design&t=cHkDPRyD6oerlgAW-1)Sponsor 9 - Phase 7 - Usability and Community Intervention on Support for Democracy and Human Rightsdonutsdonutshttps://gitlab.torproject.org/tpo/applications/vpn/-/issues/136Design the user interface for v6 of the VPN pre-alpha2024-03-27T17:31:07ZdonutsDesign the user interface for v6 of the VPN pre-alphaSee the linked issues below for specific changes and new features, each of which should include its own estimate.See the linked issues below for specific changes and new features, each of which should include its own estimate.VPN pre-alpha 06donutsdonutshttps://gitlab.torproject.org/tpo/core/arti/-/issues/1257Upgrade to educe 0.52024-02-28T14:33:54ZNick MathewsonUpgrade to educe 0.5Educe 0.5 is out; we should upgrade eventually. There are compatibility issues.Educe 0.5 is out; we should upgrade eventually. There are compatibility issues.Ian Jacksoniwj@torproject.orgIan Jacksoniwj@torproject.orghttps://gitlab.torproject.org/tpo/network-health/metrics/metrics-sql-tables/-/issues/7Rename `time` to `published` or `created` where appropriate2024-02-08T12:52:59ZGeorg KoppenRename `time` to `published` or `created` where appropriateWe have in some tables (e.g. `microdescriptor`, `bandwidth_record`, `network_status_totals`, `network_status_entry` etc.) a `time` column which can mean different things. Sometimes it's referring to a timestamp meaning the publication of...We have in some tables (e.g. `microdescriptor`, `bandwidth_record`, `network_status_totals`, `network_status_entry` etc.) a `time` column which can mean different things. Sometimes it's referring to a timestamp meaning the publication of an entry or document, sometimes it's referring to a timestamp which got set by the parser indicating the creation of the db entry.
Reading at least the descriptorParser code makes it harder when being confronted just with `time` not knowing whether it refers to some entry being published or created or whatnot at that time. So, we should rename that field accordingly, which would make it easier to match the database layout with the Tor specification as well (there are cases where the spec talks about a descriptor being published and other tools, like stem, have a `published` field, yet in our DB there is currently just `time` available).Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/network-health/team/-/issues/344Deal with EOL 0.4.7.x relays and bridges2024-03-26T17:08:10ZGeorg KoppenDeal with EOL 0.4.7.x relays and bridges0.4.7.x will be EOL on 2024-01-31. We should do the usual dance of notifying relay operators who still have not upgraded by then and then reject the relays/bridges from the network.
/cc @gus0.4.7.x will be EOL on 2024-01-31. We should do the usual dance of notifying relay operators who still have not upgraded by then and then reject the relays/bridges from the network.
/cc @gusGusGushttps://gitlab.torproject.org/tpo/core/arti-doc-project-2023/-/issues/83Deploying Arti Documentation2024-03-05T15:10:55ZpkafeiDeploying Arti DocumentationOur team is almost finished with the Arti documentation, and we are now in the process of deploying the site. We suggest deploying Arti in the current repo that it's located in using [Gitlab Pages](https://docs.gitlab.com/ee/user/project...Our team is almost finished with the Arti documentation, and we are now in the process of deploying the site. We suggest deploying Arti in the current repo that it's located in using [Gitlab Pages](https://docs.gitlab.com/ee/user/project/pages/).
We think this is the most convenient approach, but there are several issues we want to clear up before we proceed:
1. Is the [current documentation site](https://tpo.pages.torproject.net/core/arti/) repo located [here](https://gitlab.torproject.org/tpo/core/arti-doc-project-2023/-/tree/main/doc)? If so, is there a compelling reason for us to point the new docs to this new location and deploy them from the docs directory?
2. How do we handle the domain name? Will the new documentation have a new domain name?
Thanks, and let us know if we're missing anything! cc @gaba @oluchinwenyi @charlie-doc-writerAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/tpo/community/policies/-/issues/16Write a proposal for acceptable/unacceptable sustainability/incentivization o...2024-03-13T14:33:03ZGeorg KoppenWrite a proposal for acceptable/unacceptable sustainability/incentivization of relay operationsFollowing the ATOR incident we should write a proposal about what we expect from schemes claiming to enhance the sustainability of relay operations by providing (a bunch of) incentives. For some recent blog post around this topic, see: h...Following the ATOR incident we should write a proposal about what we expect from schemes claiming to enhance the sustainability of relay operations by providing (a bunch of) incentives. For some recent blog post around this topic, see: https://blog.torproject.org/tor-network-community-health-update/GusGushttps://gitlab.torproject.org/tpo/network-health/metrics/descriptorParser/-/issues/72Ingestion of new documents is busted2024-03-08T15:24:01ZGeorg KoppenIngestion of new documents is bustedWe have seen twice now that the ingestion of any new document (at least relay descriptor related) gets stopped for unknown reasons. At the time of filing this ticket (around 1200UTC 12/21/2023) the latest consensus in `/srv/parser.torpro...We have seen twice now that the ingestion of any new document (at least relay descriptor related) gets stopped for unknown reasons. At the time of filing this ticket (around 1200UTC 12/21/2023) the latest consensus in `/srv/parser.torproject.org/parser/descriptors/relay-descriptors/consensuses` is from 2023-12-20-15-00-00. Similarly, the latest bandwidth file in the `bandwidth` dir is from 2023-12-20-14-39-20.
I've seen twice thousands of errors like the following that might be related:
```
2023-12-20 15:50:55,931 INFO o.t.m.d.u.PsqlConnector:46 Connected to the PostgreSQL server successfully.
2023-12-20 15:50:56,684 WARN o.t.m.d.p.BandwidthParser:439 ERROR: duplicate key value violates unique constraint "bandwidth_record_pkey"
Detail: Key (digest, "time")=(gljFd57/3Qns/uesG7Zgwt1BhzROYK2YjG7Zl4tRHVw, 2023-11-21 01:06:42) already exists.
2023-12-20 15:50:56,687 WARN o.t.m.d.p.BandwidthParser:439 ERROR: duplicate key value violates unique constraint "bandwidth_record_pkey"
Detail: Key (digest, "time")=(rvuNn33OeoRBczYP6xTfbxZyzsM50xL1u80o0T3Z+/o, 2023-11-20 18:33:47) already exists.
2023-12-20 15:50:56,689 WARN o.t.m.d.p.BandwidthParser:439 ERROR: duplicate key value violates unique constraint "bandwidth_record_pkey"
```
However, I was unable to find other logs that might indicate better what the actual problem is.HiroHirohttps://gitlab.torproject.org/tpo/network-health/metrics/onionperf/-/issues/40072op-de8a-conflux is not producing any clear net measurements it seems2024-01-25T14:25:04ZGeorg Koppenop-de8a-conflux is not producing any clear net measurements it seemsWhile still in the .csv file `op-de8a-conflux` does not produce any clear net measurements it seems according to the attached .csv file ([torperf-2023-11-01-2023-12-21-public-5mb.csv](/uploads/c4f34a39811c58d3c15cb2843d1c94bf/torperf-202...While still in the .csv file `op-de8a-conflux` does not produce any clear net measurements it seems according to the attached .csv file ([torperf-2023-11-01-2023-12-21-public-5mb.csv](/uploads/c4f34a39811c58d3c15cb2843d1c94bf/torperf-2023-11-01-2023-12-21-public-5mb.csv)) for the 5MB downloads. Onion service measurements seem to be fine, though.HiroHirohttps://gitlab.torproject.org/tpo/network-health/metrics/networkstatusapi/-/issues/17get total relays/bridges from database2023-12-19T16:37:28ZMattia Righettiget total relays/bridges from databaseThis way we don't have to update the configuration file from which these have been retrieved up until nowThis way we don't have to update the configuration file from which these have been retrieved up until nowMattia RighettiMattia Righettihttps://gitlab.torproject.org/tpo/network-health/metrics/networkstatusapi/-/issues/13Wrong`relays_truncated` value when no limit is specified2023-12-13T21:30:26ZMattia RighettiWrong`relays_truncated` value when no limit is specifiedMattia RighettiMattia Righettihttps://gitlab.torproject.org/tpo/community/outreach/-/issues/40053Review and update the street team kit2024-03-25T22:29:02ZdonutsReview and update the street team kitMany of the materials that are part of the [Street Team Kit](https://community.torproject.org/outreach/kit/) are out of date (from a brand/design POV), designed for print, and/or cannot be updated because the original working files are l...Many of the materials that are part of the [Street Team Kit](https://community.torproject.org/outreach/kit/) are out of date (from a brand/design POV), designed for print, and/or cannot be updated because the original working files are long gone. As such, we should:
- Review the list to decide on which materials we want to keep and update, and in what order.
- Update each to match our new brand guidelines, when ready.
- Update the layouts so they're suitable for both digital use and print.
- Implement feedback from LATAM partners collected here: https://gitlab.torproject.org/tpo/ux/research/-/issues/22#note_2825275
- Improve accessibility where possible—I believe some of these were originally done in Sketch, so text recognition/text to speech may not be great.
I don't expect we'll be able to redo all of these materials in a single phase, however.Sponsor 9 - Phase 7 - Usability and Community Intervention on Support for Democracy and Human Rightsnicobnicobhttps://gitlab.torproject.org/tpo/core/tor/-/issues/40893New conflux links every 30 sec when unused connections2024-01-25T21:08:13ZcypherpunksNew conflux links every 30 sec when unused connectionsAbout 30? minutes without use when tor drops the last connection, it creates 6 new Conflux_linked connections that drops after 30 seconds. Then replaces them with a new set of 6 Conflux_linked only for 30 seconds. And continues this loo...About 30? minutes without use when tor drops the last connection, it creates 6 new Conflux_linked connections that drops after 30 seconds. Then replaces them with a new set of 6 Conflux_linked only for 30 seconds. And continues this loop for ever until normal tor use is resumed.
latest commit tested: cec6f9919d3128646d85c75d08338bea4b31bffa
linux 6.4
This behavior exist at least a couple of months, before the adoption of the 4.8 series from the tor browser.Tor: 0.4.8.x-post-stableMike PerryMike Perryhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42280Weird connection attempt to multicast IPv6 ff00:::443 on "New identity"2024-01-09T13:50:38ZintrigeriWeird connection attempt to multicast IPv6 ff00:::443 on "New identity"First of all, my apologies, it's not trivial for me to reproduce with a pristine Tor Browser (I would need to learn how to log SOCKS activity in Tor Browser or tor daemon, without the facilities we have in Tails), so I did not yet. I'm h...First of all, my apologies, it's not trivial for me to reproduce with a pristine Tor Browser (I would need to learn how to log SOCKS activity in Tor Browser or tor daemon, without the facilities we have in Tails), so I did not yet. I'm hoping a Tor Browser developer can very cheaply confirm whether this happens in a pristine Tor Browser (if not, feel free to reject and I'll see what we can do about it in Tails :)
This was reported by a Tails user and I reproduced it on my Debian sid + Tor Browser configured to use the system tor daemon + OnionCircuits.
When I do "New identity", I see request for Tor circuits to ff00:::443. The logs from Tails onion-grater (our Tor control port filter daemon) say:
```
650 STREAM 18 NEW 0 ff00:::443 SOURCE_ADDR=10.200.1.2:35108 PURPOSE=USER SOCKS_USERNAME="3118f03f-a085-41ca-abda-8f54eddf88f8.mozilla:0" SOCKS_PASSWORD="9d4853a3dc5ad1f8df87a8451828d99db03999010eff468f67e4ff0cfc3484fb" CLIENT_PROTOCOL=SOCKS5 NYM_EPOCH=0 SESSION_GROUP=-7 ISO_FIELDS=SOCKS_USERNAME,SOCKS_PASSWORD,CLIENTADDR,SESSION_GROUP,NYM_EPOCH
650 STREAM 18 SENTCONNECT 8 ff00:::443 SOCKS_USERNAME="3118f03f-a085-41ca-abda-8f54eddf88f8.mozilla:0" SOCKS_PASSWORD="9d4853a3dc5ad1f8df87a8451828d99db03999010eff468f67e4ff0cfc3484fb" CLIENT_PROTOCOL=SOCKS5 NYM_EPOCH=0 SESSION_GROUP=-7 ISO_FIELDS=SOCKS_USERNAME,SOCKS_PASSWORD,CLIENTADDR,SESSION_GROUP,NYM_EPOCH
650 STREAM 19 NEW 0 ff00:::443 SOURCE_ADDR=10.200.1.2:35124 PURPOSE=USER SOCKS_USERNAME="3118f03f-a085-41ca-abda-8f54eddf88f8.mozilla:0" SOCKS_PASSWORD="9d4853a3dc5ad1f8df87a8451828d99db03999010eff468f67e4ff0cfc3484fb" CLIENT_PROTOCOL=SOCKS5 NYM_EPOCH=0 SESSION_GROUP=-7 ISO_FIELDS=SOCKS_USERNAME,SOCKS_PASSWORD,CLIENTADDR,SESSION_GROUP,NYM_EPOCH
650 STREAM 19 SENTCONNECT 8 ff00:::443 SOCKS_USERNAME="3118f03f-a085-41ca-abda-8f54eddf88f8.mozilla:0" SOCKS_PASSWORD="9d4853a3dc5ad1f8df87a8451828d99db03999010eff468f67e4ff0cfc3484fb" CLIENT_PROTOCOL=SOCKS5 NYM_EPOCH=0 SESSION_GROUP=-7 ISO_FIELDS=SOCKS_USERNAME,SOCKS_PASSWORD,CLIENTADDR,SESSION_GROUP,NYM_EPOCH
650 STREAM 18 REMAP 8 [ff00::]:443 SOCKS_USERNAME="3118f03f-a085-41ca-abda-8f54eddf88f8.mozilla:0" SOCKS_PASSWORD="9d4853a3dc5ad1f8df87a8451828d99db03999010eff468f67e4ff0cfc3484fb" CLIENT_PROTOCOL=SOCKS5 NYM_EPOCH=0 SESSION_GROUP=-7 ISO_FIELDS=SOCKS_USERNAME,SOCKS_PASSWORD,CLIENTADDR,SESSION_GROUP,NYM_EPOCH
650 STREAM 18 DETACHED 8 [ff00::]:443 REASON=END REMOTE_REASON=EXITPOLICY SOCKS_USERNAME="3118f03f-a085-41ca-abda-8f54eddf88f8.mozilla:0" SOCKS_PASSWORD="9d4853a3dc5ad1f8df87a8451828d99db03999010eff468f67e4ff0cfc3484fb" CLIENT_PROTOCOL=SOCKS5 NYM_EPOCH=0 SESSION_GROUP=-7 ISO_FIELDS=SOCKS_USERNAME,SOCKS_PASSWORD,CLIENTADDR,SESSION_GROUP,NYM_EPOCH
650 STREAM 18 SENTCONNECT 8 [ff00::]:443 SOCKS_USERNAME="3118f03f-a085-41ca-abda-8f54eddf88f8.mozilla:0" SOCKS_PASSWORD="9d4853a3dc5ad1f8df87a8451828d99db03999010eff468f67e4ff0cfc3484fb" CLIENT_PROTOCOL=SOCKS5 NYM_EPOCH=0 SESSION_GROUP=-7 ISO_FIELDS=SOCKS_USERNAME,SOCKS_PASSWORD,CLIENTADDR,SESSION_GROUP,NYM_EPOCH
```
I understand the network rejects these attempts (`EXITPOLICY`), which is great. I understand ff00::/8 that's because is supposed to be local. But I suppose that ideally Tor Browser should not even ask tor to connect there.
I lack IPv6 expertise to tell how bad this is.
Interestingly I see no such connection attempt when first starting Tor Browser.ma1ma1https://gitlab.torproject.org/tpo/network-health/metrics/descriptorParser/-/issues/59Make a md file about reproducible metrics2024-01-16T13:49:10ZHiroMake a md file about reproducible metricsOn metrics.tpo we have a page about reproducible metrics, where it is explained how it is possible to reproduce the graphs that are published on the website (https://metrics.torproject.org/reproducible-metrics.html). The same graphs can ...On metrics.tpo we have a page about reproducible metrics, where it is explained how it is possible to reproduce the graphs that are published on the website (https://metrics.torproject.org/reproducible-metrics.html). The same graphs can be obtained in grafana or via querying victoriametrics directly, but people need to experiment a bit and understand how to extract data from timeseries.
We should have a file to explain how to recreate that aggregated data from timeseries on VM.HiroHirohttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41004Auto-build Tor + Mullvad Browsers on tag push2023-11-06T23:11:00ZrichardAuto-build Tor + Mullvad Browsers on tag pushWe chatted briefly last week about Mullvad somehow auto-building our browsers on tag push.
We would like to bring Mullvad into the build release verification process (eg as another builder) to give users further confidence that devs ar...We chatted briefly last week about Mullvad somehow auto-building our browsers on tag push.
We would like to bring Mullvad into the build release verification process (eg as another builder) to give users further confidence that devs are not collaborating to sneak malicious code into the build.
/cc @ruihildtjbjorkangjbjorkang