The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2022-09-07T07:01:44Zhttps://gitlab.torproject.org/tpo/network-health/doctor/-/issues/40017Doctor incorrectly reports clock skew2022-09-07T07:01:44ZRoger DingledineDoctor incorrectly reports clock skewOn the consensus-health mails, we're getting lines like this:
```
NOTICE: The system clock of moria1 is 48 seconds off
NOTICE: The system clock of dizum is 70 seconds off
NOTICE: The system clock of Faravahar is 37 seconds off
NOTICE: Th...On the consensus-health mails, we're getting lines like this:
```
NOTICE: The system clock of moria1 is 48 seconds off
NOTICE: The system clock of dizum is 70 seconds off
NOTICE: The system clock of Faravahar is 37 seconds off
NOTICE: The system clock of longclaw is 41 seconds off
```
But I believe the clocks on these systems are fine.
What I assume is happening is that DocTor is launching a directory fetch for an object like the consensus, and it's taking 48 seconds to finish retrieving the answer, and then DocTor looks at the Date header in the resulting http response, notices that it is from 48 seconds ago, and reports a clock problem.
Here is an improved algorithm: remember when we started the request, and when we finished it, and if the Date header is anywhere within that range, there is nothing to report.
We could instead consider making additional tiny requests where we expect the answer to come back quickly, but I think that might be overkill at this stage.https://gitlab.torproject.org/tpo/anti-censorship/emma/-/issues/6Maybe try more than once if a connection timed out?2021-02-07T21:57:09ZPhilipp Winterphw@torproject.orgMaybe try more than once if a connection timed out?I tried to make sense of recent emma runs in Uganda (see tpo/community/outreach#40007) and noticed that it's difficult to tell if a connection failed because of reliability issues or because of censorship. Emma currently tries once to [e...I tried to make sense of recent emma runs in Uganda (see tpo/community/outreach#40007) and noticed that it's difficult to tell if a connection failed because of reliability issues or because of censorship. Emma currently tries once to [establish a TCP connection](https://gitlab.torproject.org/tpo/anti-censorship/emma/-/blob/2ed24be87ec7b6988ebc3c3723e53a2f7f17f89d/tests.go#L36) to a target and if that fails, it labels the target as unreachable. It's up to the operating system to determine the number of TCP retransmissions. Let's teach emma to try more than once to establish a TCP connection to a target. This will increase the test time a little bit but I think the improved clarity is worth the additional wait time.https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/14Listing microseconds in bridgestrap status output is confusing2021-06-10T14:16:52ZRoger DingledineListing microseconds in bridgestrap status output is confusing(This ticket is just a simple UX improvement, but hopefully still a useful one :) I've tagged it as 'First Contribution' since it's a good opportunity for somebody to get some experience making a git commit etc.)
Compare the current out...(This ticket is just a simple UX improvement, but hopefully still a useful one :) I've tagged it as 'First Contribution' since it's a good opportunity for somebody to get some experience making a git commit etc.)
Compare the current output format:
```
* obfs4: dysfunctional
Error: timed out waiting for bridge descriptor
Last tested: 2021-01-17 10:38:22.671859857 +0000 UTC (8h41m42.941665234s ago)
```
to this simpler alternative:
```
* obfs4: dysfunctional
Error: timed out waiting for bridge descriptor
Last tested: 2021-01-17 10:38:22 +0000 UTC (8h41m42s ago)
```
At present, having so much precision in the fraction of the seconds draws the reader's eye to that number, and that number is the least important part of the output.
Thanks!https://gitlab.torproject.org/tpo/web/lego/-/issues/21Add Privchat to footer?2021-08-31T13:25:14ZdonutsAdd Privchat to footer?There doesn't seem to be a way to navigate to the [Privchat landing page](https://www.torproject.org/privchat/) via the site menus. Adding a link to the footer seems like a sensible solution.There doesn't seem to be a way to navigate to the [Privchat landing page](https://www.torproject.org/privchat/) via the site menus. Adding a link to the footer seems like a sensible solution.https://gitlab.torproject.org/tpo/web/support/-/issues/157Missing dot at the end2021-01-07T14:32:28ZGusMissing dot at the end"You can also access the New Circuit option inside the site information menu in the URL bar, and the New Identity option by
clicking the small sparky broom icon at the top-right of the screen"
https://support.torproject.org/tbb/tbb-29/"You can also access the New Circuit option inside the site information menu in the URL bar, and the New Identity option by
clicking the small sparky broom icon at the top-right of the screen"
https://support.torproject.org/tbb/tbb-29/https://gitlab.torproject.org/tpo/web/support/-/issues/156Update how to manage bookmarks2021-04-06T09:55:13ZGusUpdate how to manage bookmarksAfter TB 10, these instructions need to be updated:
https://support.torproject.org/tbb/export-and-import-bookmarks/After TB 10, these instructions need to be updated:
https://support.torproject.org/tbb/export-and-import-bookmarks/https://gitlab.torproject.org/tpo/core/tor/-/issues/40232"Closing no-longer-configured OR listener" does not put brackets around IPv6 ...2021-07-09T17:22:52ZNeel Chauhanneel@neelc.org"Closing no-longer-configured OR listener" does not put brackets around IPv6 addressesWhen I was setting `IPv4Only` on a new Tor relay with broken IPv6, and did `killall -HUP tor`, I got this:
Dec 23 20:08:02.000 [notice] Closing no-longer-configured OR listener on :::143
(I believe) the `:::143` should be `[::]:143`.When I was setting `IPv4Only` on a new Tor relay with broken IPv6, and did `killall -HUP tor`, I got this:
Dec 23 20:08:02.000 [notice] Closing no-longer-configured OR listener on :::143
(I believe) the `:::143` should be `[::]:143`.https://gitlab.torproject.org/tpo/anti-censorship/emma/-/issues/5Incorporate emma into OONI2024-02-29T15:21:09ZPhilipp Winterphw@torproject.orgIncorporate emma into OONIMaria once suggested adding emma to OONI. Both are written in Go, so it may not be a terribly complex endeavour. I'll have a chat with Simone to get a better sense of what this would entail.
The big benefit of having emma in OONI is th...Maria once suggested adding emma to OONI. Both are written in Go, so it may not be a terribly complex endeavour. I'll have a chat with Simone to get a better sense of what this would entail.
The big benefit of having emma in OONI is that we would get significantly more measurements and we no longer need to expect users to be able to compile programs.https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues/6Add "end-to-end" test that talks to moat2022-03-01T17:56:58ZPhilipp Winterphw@torproject.orgAdd "end-to-end" test that talks to moatTo catch issues like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we could add a new monit test that talks to moat over obfs4proxy. Basically, we would spawn a tor instance and let it bootstrap over meek. We then...To catch issues like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we could add a new monit test that talks to moat over obfs4proxy. Basically, we would spawn a tor instance and let it bootstrap over meek. We then try to talk to moat and return with exit code 0 if this succeeded.
The challenge is that we should use the same tor and obfs4proxy version as Tor Browser does. And even then, there is no guarantee that we're catching all possible problems – for example, an issue may be limited to Windows. Still, having a test like this would probably go a long way.
(We discussed this topic in [today's anti-censorship meeting](http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-12-17-15.57.html)).https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/issues/5Monitor meek bridge's usage numbers and alert if it falls below threshold2021-06-10T14:12:56ZPhilipp Winterphw@torproject.orgMonitor meek bridge's usage numbers and alert if it falls below thresholdTo make sure that we catch problems like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we should put a system in place that monitors the usage numbers of our [meek bridge](https://metrics.torproject.org/rs.html#de...To make sure that we catch problems like the one in tpo/anti-censorship/pluggable-transports/meek#40001 early, we should put a system in place that monitors the usage numbers of our [meek bridge](https://metrics.torproject.org/rs.html#details/8F4541EEE3F2306B7B9FEF1795EC302F6B84DAE8) and alerts us if the numbers fall below a given threshold.
Here's what obfs4proxy's recent public key pinning issue looked like on our meek bridge:
![image](/uploads/449f3698b2c13eaf1461d10fcfe2496c/image.png)
We could regularly fetch the bridge's extrainfo descriptors and extract its usage numbers but there may be a better way to go about this.https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40186noto-fonts Git repo is excessively large2022-12-08T15:15:28ZJeremyRandnoto-fonts Git repo is excessively largeThe `noto-fonts` Git repo (cloned as part of the `fonts` project) uses over 6 GiB of storage, even though downloading a `.zip` archive from GitHub of the tree at that commit hash results in an archive that uses less than 40 MiB when deco...The `noto-fonts` Git repo (cloned as part of the `fonts` project) uses over 6 GiB of storage, even though downloading a `.zip` archive from GitHub of the tree at that commit hash results in an archive that uses less than 40 MiB when decompressed. Is there any reason that it's downloaded via Git rather than a standard HTTPS archive download? The excessively large size is a significant barrier to some users with limited storage capacity and/or network bandwidth.https://gitlab.torproject.org/tpo/community/l10n/-/issues/40016Cannot choose language on mobile2021-03-02T10:33:39ZstephwCannot choose language on mobileThe entire language list is not accessible on mobile.
https://twitter.com/glotzbach/status/1111165746623799296The entire language list is not accessible on mobile.
https://twitter.com/glotzbach/status/1111165746623799296https://gitlab.torproject.org/tpo/web/newsletter/-/issues/11https://newsletter.torproject.org overlaps text as width is too small on my p...2021-10-08T06:22:07ZGeorg Koppenhttps://newsletter.torproject.org overlaps text as width is too small on my phoneTesting on a Samsungs Galaxy S5 mini I realized there is overlapping text on https://newsletter.torproject.org in the Archive section (the dates overlap with text so that the result is hardly readable). See attachment for how this looks ...Testing on a Samsungs Galaxy S5 mini I realized there is overlapping text on https://newsletter.torproject.org in the Archive section (the dates overlap with text so that the result is hardly readable). See attachment for how this looks like.https://gitlab.torproject.org/tpo/web/manual/-/issues/71TB manual single page2022-05-04T16:05:47Zweasel (Peter Palfrader)TB manual single pageCan we please (additionally if you like) have a single-page build of the manual?Can we please (additionally if you like) have a single-page build of the manual?https://gitlab.torproject.org/tpo/web/support/-/issues/147Tor Browser Developer key is available on keys.openpgp.net2021-03-01T17:28:10ZGusTor Browser Developer key is available on keys.openpgp.netSince the key is now available on keys.openpgp.org:
https://keys.openpgp.org/search?q=torbrowser%40torproject.org
We should add this to How to verify signature: https://support.torproject.org/tbb/how-to-verify-signature/Since the key is now available on keys.openpgp.org:
https://keys.openpgp.org/search?q=torbrowser%40torproject.org
We should add this to How to verify signature: https://support.torproject.org/tbb/how-to-verify-signature/championquizzerchampionquizzer@torproject.orgchampionquizzerchampionquizzer@torproject.orghttps://gitlab.torproject.org/tpo/web/tpo/-/issues/123Update /press link2020-12-21T17:21:06ZGusUpdate /press link> I can see our blog is listed here: https://www.torproject.org/press/ as a link to an article on techlector.com. I am glad to see that. However, we have rebranded our domain from techlector.com to techreen.com. Could you please re-edit ...> I can see our blog is listed here: https://www.torproject.org/press/ as a link to an article on techlector.com. I am glad to see that. However, we have rebranded our domain from techlector.com to techreen.com. Could you please re-edit this so that the old link (https://techlector.com/tor-project-will-transfer-to-azure-to-continue-offering-domain-fronting/) will be changed to https://techreen.com/tor-project-will-transfer-to-azure-to-continue-offering-domain-fronting/?GusGushttps://gitlab.torproject.org/tpo/web/community/-/issues/173Typo lins -> lines2020-12-14T21:59:27ZGusTypo lins -> linesA translator reported:
> "You can simply add it next to the first ORPort lins in your torrc file."
I guess, the word "lins" in the original text is actually "lines".A translator reported:
> "You can simply add it next to the first ORPort lins in your torrc file."
I guess, the word "lins" in the original text is actually "lines".GusGushttps://gitlab.torproject.org/tpo/web/manual/-/issues/63Images overflow on mobile2023-04-23T15:18:56ZtorrrrrrrrrrrrrrrrImages overflow on mobileOn these pages,
- https://tb-manual.torproject.org/about/
- https://tb-manual.torproject.org/secure-connections/
- https://tb-manual.torproject.org/updating/
- https://tb-manual.torproject.org/uninstalling/
An image overflows device wid...On these pages,
- https://tb-manual.torproject.org/about/
- https://tb-manual.torproject.org/secure-connections/
- https://tb-manual.torproject.org/updating/
- https://tb-manual.torproject.org/uninstalling/
An image overflows device width on mobile.
One screenshot:
<img src="/uploads/19177e9a09d6798a5a57b059d0b604ee/tb-manual.png" width="300">https://gitlab.torproject.org/tpo/core/arti/-/issues/35Refactor buffers in tor-dirclient/src/lib.rs2021-08-02T05:30:07ZNick MathewsonRefactor buffers in tor-dirclient/src/lib.rsRight now, the buffer used in tor-dirclient/src/lib.rs is a `Vec<u8>`, and the code copies around inside it a lot.
It might be cool to change that to be a VecDeque<u8> instead, and not have to copy inside the buffer.Right now, the buffer used in tor-dirclient/src/lib.rs is a `Vec<u8>`, and the code copies around inside it a lot.
It might be cool to change that to be a VecDeque<u8> instead, and not have to copy inside the buffer.https://gitlab.torproject.org/tpo/core/arti/-/issues/34Add support for more compression types2021-01-21T17:04:19ZNick MathewsonAdd support for more compression typesRight now the directory code in `tor-dirclient/src/compress.rs` supports zlib compression only. It would be good to add support for ~~xz2 and~~ zstd and maybe brotli.
Update (17 Dec 2020): @wuldr has added support for xz2!Right now the directory code in `tor-dirclient/src/compress.rs` supports zlib compression only. It would be good to add support for ~~xz2 and~~ zstd and maybe brotli.
Update (17 Dec 2020): @wuldr has added support for xz2!