The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2022-05-05T20:24:17Zhttps://gitlab.torproject.org/tpo/web/tpo/-/issues/296Link URL on homepage being translated2022-05-05T20:24:17ZKezLink URL on homepage being translatedLavamind found that the "Meet our team" link under the "ABOUT US" section on the homepage is translated under the ka locale. The link should point to `https://www.torproject.org/about/people` but is instead pointing to `https://www.torpr...Lavamind found that the "Meet our team" link under the "ABOUT US" section on the homepage is translated under the ka locale. The link should point to `https://www.torproject.org/about/people` but is instead pointing to `https://www.torproject.org/ka/%E1%83%A9%E1%83%95%E1%83%94%E1%83%9C%20%E1%83%A8%E1%83%94%E1%83%A1%E1%83%90%E1%83%AE%E1%83%94%E1%83%91/%E1%83%AE%E1%83%90%E1%83%9A%E1%83%AE%E1%83%98`https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40246Links to Wikipedia from Duckduckgo search do not work in macOS using Tor2020-11-23T08:10:31ZjenknessLinks to Wikipedia from Duckduckgo search do not work in macOS using TorLinks to Wikipedia from Duckduckgo search do not work in macOS via click, double-click, Open in Link in New Tab, or Open Link in New Window for macOS. This does not occur in other search engines, nor does it occur on a non-Tor web brows...Links to Wikipedia from Duckduckgo search do not work in macOS via click, double-click, Open in Link in New Tab, or Open Link in New Window for macOS. This does not occur in other search engines, nor does it occur on a non-Tor web browser using Duckduckgo. This issue does not seem exist for Tor in Windows 10 or Ubuntu after doing a cursory check.
**Reproducing the issue.**
Search for anything that will have a Wikipedia entry on Duckduckgo.com such as "amazon", then do any of the following to the Wikipedia link:
1. Click or double-click the link, whether in the main column or the right column, and it will not load the page.
2. Select "Open Link in New Tab" in context menu or Cmd+click on the link, and it brings up new tab with the URL, but does not automatically load the page.
3. Select "Open Link in New Window" in context menu or Shift+click, and it opens up a new blank window with nothing in the URL.
**Further details.**
10.0.5 (based on Mozilla Firefox 78.5.0esr) (64-bit),
macOS 10.13.6 (17G2208)https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/36Lockscreen, screensaver disabled while a proxy session is active2022-09-28T21:30:47ZpromeneurLockscreen, screensaver disabled while a proxy session is activeopenSUSE 15.3
Chrome 96
snowflake 0.5.4
When someone uses snowflake and uses webrtc protocol
then
my PC lokscreen and screensaver are disabled.
It's normal if I use webrtc but not if someone uses webrtc via snowflake.openSUSE 15.3
Chrome 96
snowflake 0.5.4
When someone uses snowflake and uses webrtc protocol
then
my PC lokscreen and screensaver are disabled.
It's normal if I use webrtc but not if someone uses webrtc via snowflake.https://gitlab.torproject.org/tpo/tpa/team/-/issues/41439Logging into forum with 2FA leads to "UnknownError: The operation failed for ...2023-12-12T15:32:45ZGeorg KoppenLogging into forum with 2FA leads to "UnknownError: The operation failed for an unknown transient reason"For a while now I always get "UnknownError: The operation failed for an unknown transient reason" when I try to use my Yuikey Security Key as a second factor. I am living on backup codes right now. :) I remember transitioning to the self...For a while now I always get "UnknownError: The operation failed for an unknown transient reason" when I try to use my Yuikey Security Key as a second factor. I am living on backup codes right now. :) I remember transitioning to the self-hosted forum worked which is why I have now two keys registered in my user profile. The setup broke later for me.
Trying to register yet another key fails as I get asked for a PIN which I don't have.
Needless to say that the same key is working fine as an U2F means for Gitlab and our NextCloud instance using the same Tor Browser.
I got reminded here by https://forum.torproject.org/t/please-recover-my-account-2-factor-auth-broken/10434/4 although I am not sure whether the problem mentioned there is exactly the same to mine.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/21802Login failure with Tor Browser: Error loading content, try again.2021-03-18T11:47:11ZTracLogin failure with Tor Browser: Error loading content, try again.Hi,
I'll try to rejoin on this site (http://www.l2amerika.com/#!/vote/vote), but i can't log in anymore there. I get this message from the site "**Error loading content, try again.**"
**IMAGE:** https://postimg.org/image/xvsz53sxz/
**...Hi,
I'll try to rejoin on this site (http://www.l2amerika.com/#!/vote/vote), but i can't log in anymore there. I get this message from the site "**Error loading content, try again.**"
**IMAGE:** https://postimg.org/image/xvsz53sxz/
**Trac**:
**Username**: CodyRohttps://gitlab.torproject.org/tpo/core/tor/-/issues/17147long-running client path-selection not seeing some (fast) exit nodes2022-06-17T18:55:26Zstarlightlong-running client path-selection not seeing some (fast) exit nodesI noticed that a couple of fast new exit relays
were never being chosen, which is strange
because with an exit probability of over 1%
that should happen once in awhile.
Then used `setconf ExitNodes=` to force one
of them and the client ...I noticed that a couple of fast new exit relays
were never being chosen, which is strange
because with an exit probability of over 1%
that should happen once in awhile.
Then used `setconf ExitNodes=` to force one
of them and the client balked, saying
```
All routers are down or won't exit -- choosing a doomed exit at random.
No specified exit routers seem to be running: can't choose an exit.
Failed to choose an exit server
```
Then restarted the client and it worked.
Client was running uninterrupted for 10 days when this occurred.
`torrc` specifies `UseMicrodescriptors 0` (due to various
other misbehaviors related to running with micro-descriptors
enabled.
This appears to be an area in need of QA work.https://gitlab.torproject.org/tpo/core/tor/-/issues/29743Long-running tor instances fail to keep up-to-date directory information2022-06-17T18:54:59ZKarsten LoesingLong-running tor instances fail to keep up-to-date directory informationWe have a small number of long-running tor instances as part of our OnionPerf setups that are running 24/7. In the past, some of these tor instances got into a state where their directory information was no longer up-to-date enough to bu...We have a small number of long-running tor instances as part of our OnionPerf setups that are running 24/7. In the past, some of these tor instances got into a state where their directory information was no longer up-to-date enough to build circuits. In some cases they recovered after hours, days, or even weeks, but in some cases we had to restart the tor processes.
I'm attaching a graph that shows the number of open circuits as reported in heartbeat log messages. That number is relatively stable most of the time, depending on whether we're using the tor instance for making requests or for providing an onion service. But in some cases the number drops to zero, which coincides with the log message:
```
[notice] Our directory information is no longer up-to-date enough to build circuits: [...]
```
The graph also shows that sometimes the number magically goes up again. Those times coincide with the following log message:
```
[notice] We now have enough directory information to build circuits.
```
The purple dashed lines show when we restarted tor processes manually. Some of these restarts are unrelated to the number of open circuits. But some restarts happened explicitly because the tor instance was not working anymore for our measurements.
By the way, the op-nl instance shown in the middle was running 0.2.9.11-dev, whereas the op-us and op-hk instances were running 0.3.0.7-dev. It may be coincidence, but the older op-nl did not run out of up-to-date directory information, whereas the newer op-us and op-hk did. Was this issue maybe introduced in 0.3.0.x?
I have tor logs available for all these tor instances. I can easily provide them, either as a big tarball or for specific days and instances as a smaller tarball. Just let me know.https://gitlab.torproject.org/tpo/community/support/-/issues/40074Looping Tor2022-08-19T19:09:50ZAlexPrLooping Torsystemd restart loop `tor@default.service` every 60 seconds. Ubuntu system. Did a complete reinstallation of the system and the tor has the same error. Torcc is default. Journalctl -xe is show
```
-- The job identifier is 65029. ...systemd restart loop `tor@default.service` every 60 seconds. Ubuntu system. Did a complete reinstallation of the system and the tor has the same error. Torcc is default. Journalctl -xe is show
```
-- The job identifier is 65029.
Apr 13 04:18:20 Tor[77580]: Signaled readiness to systemd
Apr 13 04:18:21 Tor[77580]: Bootstrapped 5% (conn): Connecting to a relay
Apr 13 04:18:21 Tor[77580]: Opening Socks listener on /run/tor/socks
Apr 13 04:18:21 Tor[77580]: Opened Socks listener connection (ready) on /run/tor/socks
Apr 13 04:18:21 Tor[77580]: Opening Control listener on /run/tor/control
Apr 13 04:18:21 Tor[77580]: Opened Control listener connection (ready) on /run/tor/control
Apr 13 04:18:21 Tor[77580]: Bootstrapped 10% (conn_done): Connected to a relay
Apr 13 04:18:21 Tor[77580]: Bootstrapped 14% (handshake): Handshaking with a relay
Apr 13 04:18:21 Tor[77580]: Bootstrapped 15% (handshake_done): Handshake with a relay done
Apr 13 04:18:21 Tor[77580]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to >
Apr 13 04:18:21 Tor[77580]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a rel>
Apr 13 04:18:21 Tor[77580]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Apr 13 04:18:22 Tor[77580]: Bootstrapped 100% (done): Done
Apr 13 04:19:01 systemd[1]: tor@default.service: Main process exited, code=killed, status=9/KILL
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An ExecStart= process belonging to unit tor@default.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 9.
Apr 13 04:19:01 systemd[1]: tor@default.service: Failed with result 'signal'.
```Silvio RhattoSilvio Rhattohttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/26309Lost previous tabs when updated to 7.5.42022-02-03T19:05:22ZTracLost previous tabs when updated to 7.5.4In my previous Tor version (don't know what it was), I set Tor to open tabs from previous session on startup, keep history, etc.
Today I've updated to Tor 7.5.4. All my tabs, the history **are gone**. The setting isn't available anymore...In my previous Tor version (don't know what it was), I set Tor to open tabs from previous session on startup, keep history, etc.
Today I've updated to Tor 7.5.4. All my tabs, the history **are gone**. The setting isn't available anymore.
Why didn't I get **ANY** warning on such destructive behavior?
I know, privacy and all that stuff, but you shouldn't limit the users. Make it the default and allow customization. But anyway, you should at least notify about it. I don't use the browser for "dark" stuff - I use it just as something that allows me to open websites not available in my country.
Now I lost all my tabs. How am I supposed to restore them?
**Trac**:
**Username**: artemikhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/17244Low entropy PRNG usage in Tor Browser?2022-02-03T19:06:44ZArthur EdelsteinLow entropy PRNG usage in Tor Browser?We should look for places where Tor Browser may leak the state of a low-entropy PRNG, thus linking a user across sites. `Math.random()` is a possibility. (I haven't investigated yet.)We should look for places where Tor Browser may leak the state of a low-entropy PRNG, thus linking a user across sites. `Math.random()` is a possibility. (I haven't investigated yet.)https://gitlab.torproject.org/tpo/network-health/sbws/-/issues/40155Lower advertised bandwidth/consensus weight on relays with "higher latency"2023-07-03T13:14:12ZNeel Chauhanneel@neelc.orgLower advertised bandwidth/consensus weight on relays with "higher latency"I run four middle relays on a CenturyLink Gigabit connection in Seattle, WA: https://metrics.torproject.org/rs.html#search/neeltorrelay
I noticed that the consensus weight is lower if the latency is generally higher, with four instances...I run four middle relays on a CenturyLink Gigabit connection in Seattle, WA: https://metrics.torproject.org/rs.html#search/neeltorrelay
I noticed that the consensus weight is lower if the latency is generally higher, with four instances on a connection I get ~25 MB/s (~200 Mbps). "higher latency" means generally higher latency from most of the other relays, namely relays in Europe.
I can get around this temporally by pushing large file downloads between my relay instances, with two client instances and relays closer to my area (namely Emerald Onion, Telus, and Ziply Fiber). Right now the advertised bandwidth/consensus weight is lower than it could be.
For a while it seemed fixed, but it came back for some reason.jugajugahttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/23701Lower parts of letters get eaten by making line-height uniform2022-02-03T19:06:05ZGeorg KoppenLower parts of letters get eaten by making line-height uniformIn legacy/trac#23104 we tried to make the line height uniform in order to avoid operating system fingerprinting. It seems that affects some systems in a way that lower parts of letters in the URL bar are eaten:
https://blog.torproject.o...In legacy/trac#23104 we tried to make the line height uniform in order to avoid operating system fingerprinting. It seems that affects some systems in a way that lower parts of letters in the URL bar are eaten:
https://blog.torproject.org/tor-browser-75a5-released#comment-271522https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/25539MacOS Tor fails to restart after new download2022-02-03T19:05:48ZTracMacOS Tor fails to restart after new downloadlagtest download of 7.5.2 Tor will not restart.
**Trac**:
**Username**: neptune2000lagtest download of 7.5.2 Tor will not restart.
**Trac**:
**Username**: neptune2000https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/23337make "download" the default checked option for all types of files from downlo...2022-02-03T19:06:20ZTracmake "download" the default checked option for all types of files from download linksthere are two options in the window opening after clicking on a download link:
1. open with ...
2. download
somtimes 1. is checked, at other times 2.
downloading and opening a file offline is recommended.
suggestion: make download the d...there are two options in the window opening after clicking on a download link:
1. open with ...
2. download
somtimes 1. is checked, at other times 2.
downloading and opening a file offline is recommended.
suggestion: make download the default checked option for all files.
**Trac**:
**Username**: downloadfiles@grr.lahttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40068Make it easier to report bugs2022-02-03T19:06:45ZiotaMake it easier to report bugsHi there,
I've reported my first bug today, and the path is quite tricky. Here are two proposal to make it easier:
- make it possible to search the documentation on https://support.torproject.org
- add a reference to this bug tracker i...Hi there,
I've reported my first bug today, and the path is quite tricky. Here are two proposal to make it easier:
- make it possible to search the documentation on https://support.torproject.org
- add a reference to this bug tracker in the footer. There is a link pointing to github, but a link to https://gitlab.torproject.org is missing
Keep on the good work!
Cheershttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/22341Make sure to pick up zstd+lzma support for tor in Tor Browser2023-11-09T08:42:24ZGeorg KoppenMake sure to pick up zstd+lzma support for tor in Tor BrowserWe might need to adapt our descriptors to make sure tor in Tor Browser is built with zstd+lzma support as well.
This is the parent ticket and the work, if needed, is done in child tickets.We might need to adapt our descriptors to make sure tor in Tor Browser is built with zstd+lzma support as well.
This is the parent ticket and the work, if needed, is done in child tickets.https://gitlab.torproject.org/tpo/core/tor/-/issues/29989MapAddress directive added to torrc doesn't work for some websites, fails to ...2022-06-17T18:34:07ZTracMapAddress directive added to torrc doesn't work for some websites, fails to assign specified exit nodePlease refer to this thread on the TOR Stack Exchange:
https://tor.stackexchange.com/questions/19647/how-are-certain-websites-able-to-override-the-specific-exitnode-you-chose-and-c
If I add the following to my torrc (and restart TOR):
...Please refer to this thread on the TOR Stack Exchange:
https://tor.stackexchange.com/questions/19647/how-are-certain-websites-able-to-override-the-specific-exitnode-you-chose-and-c
If I add the following to my torrc (and restart TOR):
```
MapAddress ayefiles.com ayefiles.com.719FD0FA327F3CCBCDA0D4EA74C15EA110338942.exit
MapAddress duckduckgo.com duckduckgo.com.719FD0FA327F3CCBCDA0D4EA74C15EA110338942.exit
```
then I see that if I visit https://duckduckgo.com/, I'm correctly assigned to use exit node 185.220.100.252, which corresponds to the fingerptint. However, if I visit https://ayefiles.com, my exit node will NOT be 185.220.100.252, but instead can be any exit node such as 176.9.53.58 or 148.253.182.141, and will even change if I do a Ctrl+L to get a "New Tor circuit for this site" which should be a no-op for sites with MapAddress directives mapping them to a single exit node.
How is ayefiles.com able to hack TOR and prevent it from applying the requested exit node? Can we stop this from happening?
Finally, if for some reason this is "expected behavior" (though I can't fathom how) please change this to a feature request to add a way to specify a single exit node in a similar way to MapAddress, except that can't be hacked.
**Trac**:
**Username**: babyfarkmcgeezaxxonhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/27768Menu button does not work in Tor Browser 8 on Windows2022-02-03T19:05:22ZTracMenu button does not work in Tor Browser 8 on Windows1.As you see the highlighted part in the "help" menu is useless so please remove it
2.The "menu" button on the right doesn't open
3.As in the picture the "customize" tab is barely opens after few retries ,even though it's blank & i'm u...1.As you see the highlighted part in the "help" menu is useless so please remove it
2.The "menu" button on the right doesn't open
3.As in the picture the "customize" tab is barely opens after few retries ,even though it's blank & i'm unable to make any customize
4.Whenever i try to import my "html bookmarks" file the browser bookmarks remains ((empty)) ,also the "bookmark this page" function is broken
5.Please kindly retrieve back the "Test Tor Network Settings" feature to the "about:tor" homepage
6.Please kindly retrieve the "tor button" back it's former version
**Trac**:
**Username**: therapidhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40228method not allowed when subscribing to a newsletter2021-05-06T14:19:45Zanarcatmethod not allowed when subscribing to a newsletterparaphrasing a bug report received by email from @smith
> when I click on the confirmation address in your email to me, appears: "Method not allowed" and "Must be one of: OPTIONS"
to reproduce:
1. head to the [newsletter page](http...paraphrasing a bug report received by email from @smith
> when I click on the confirmation address in your email to me, appears: "Method not allowed" and "Must be one of: OPTIONS"
to reproduce:
1. head to the [newsletter page](https://newsletter.torproject.org/)
2. fill your email address and the captch, hit "join"
3. you'll receive an email with a link looking like: <https://donate-api.torproject.org/subscription-confirm?token=REDACTED>
4. then you'll get "Method not allowed", if you reproduce the bug
In my case, however, I get a "Subscription Confirmed", so I'm not sure what is going on here.
In any case, we're seeing a drastic reductions in the number of new subscribers since at least december 2020, but maybe as far back as november or october 2020.anarcatanarcathttps://gitlab.torproject.org/tpo/core/tor/-/issues/26933Minor memleak in HSv3 configuration2021-09-30T13:45:56ZGeorge KadianakisMinor memleak in HSv3 configurationI ran my HSv3 under valgrind for a while. I didn't find anything major.
The only interesting thing I could find is this leaked string during service configuration:
```
==13380== 26 bytes in 1 blocks are still reachable in loss record 54...I ran my HSv3 under valgrind for a while. I didn't find anything major.
The only interesting thing I could find is this leaked string during service configuration:
```
==13380== 26 bytes in 1 blocks are still reachable in loss record 545 of 654
==13380== at 0x4C2BC20: malloc (vg_replace_malloc.c:296)
==13380== by 0x2EB977: tor_malloc_ (util_malloc.c:45)
==13380== by 0x2D6946: esc_for_log (util.c:605)
==13380== by 0x2D6C3D: escaped (util.c:677)
==13380== by 0x26D26C: config_generic_service (hs_config.c:372)
==13380== by 0x26D26C: config_service (hs_config.c:471)
==13380== by 0x26D26C: hs_config_service_all (hs_config.c:555)
==13380== by 0x206996: options_validate (config.c:4384)
==13380== by 0x20AB2F: options_init_from_string (config.c:5497)
==13380== by 0x20B170: options_init_from_torrc (config.c:5273)
==13380== by 0x15B7BC: tor_init (main.c:3524)
==13380== by 0x15C23C: tor_run_main (main.c:4239)
==13380== by 0x1557A9: tor_main (tor_api.c:84)
==13380== by 0x155518: main (tor_main.c:32)
```Tor: unspecified