Hello, I use Tor Expert Bundle as my main censorship circumvention method, I also have a github repo with pre-configured Tor Expert Bundle for many Russian users (it has 90+ stars). On my second PC with Win 7 Tor Expert Bundle 0.4.8.13 doesn’t work anymore unlike 0.4.8.12. Are you completely deprecating the support for Win 7 users or can you fix this bug, please?
- It is possible to use Tor 0.4.8.13 on Windows 7:
Nov 04 13:57:58.478 [notice] Tor 0.4.8.13 (git-e153e72c01315f86) running on Windows 7 with Libevent 2.1.12-stable, OpenSSL 3.3.1, Zlib 1.3.1, Liblzma 5.6.2, Libzstd 1.5.6 and Unknown N/A as libc. - What exactly is not working? Are you getting errors? If so, which ones?
- It is possible to select for building Tor compiler which is 100% compatible with Windows 7. It may take several attempts however.
I use webtunnel bridges and there is a lyrebird crash, I can probably provide the log. If it should be possible then it is a bug that should be fixed. I’m getting warns and an error I can’t say which one for now, I need either log it in file or screenshot it. I thought the error is because tor expert is now relying on browser 14.0 version which doesn’t support Win 7 anymore.
1 Like
I can’t upload files as a new user, but I created file logs. Should I upload them with a debug or with a notice level?
Ok, so it is lyrebird which should be rebuilt then.
I explained how to create compatible Go binary:
I don’t feel like I can do anything myself, I need to contact devs. Right now I don’t even have the Gitlab account which I requested and I can’t upload any single file. I want it to be fixed in 0.4.8.14 but there is not much that I can do.
These are my two log files in notice level, since I can’t upload them as files. They are on different versions, only on of them is crashing.
0.4.8.12: (no crash)
Nov 08 01:17:40.000 [notice] Tor 0.4.8.12 (git-2beaa7557c3c93ec) opening new log file.
Nov 08 01:17:40.066 [notice] We compiled with OpenSSL 300000e0: OpenSSL 3.0.14 4 Jun 2024 and we are running with OpenSSL 300000e0: 3.0.14. These two versions should be binary compatible.
Nov 08 01:17:40.074 [notice] Tor 0.4.8.12 (git-2beaa7557c3c93ec) running on Windows 7 with Libevent 2.1.12-stable, OpenSSL 3.0.14, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Nov 08 01:17:40.074 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Nov 08 01:17:40.081 [notice] Read configuration file "C:\AntiTor\torrc.txt".
Nov 08 01:17:40.082 [warn] Path for CacheDirectory (..\data) is relative and will resolve to C:\AntiTor\data. Is this what you wanted?
Nov 08 01:17:40.082 [warn] Path for DataDirectory (..\data) is relative and will resolve to C:\AntiTor\data. Is this what you wanted?
Nov 08 01:17:40.082 [warn] Path for GeoIPFile (..\data\geoip) is relative and will resolve to C:\AntiTor\data\geoip. Is this what you wanted?
Nov 08 01:17:40.082 [warn] Path for GeoIPv6File (..\data\geoip6) is relative and will resolve to C:\AntiTor\data\geoip6. Is this what you wanted?
Nov 08 01:17:40.084 [notice] Opening Socks listener on 127.0.0.1:9050
Nov 08 01:17:40.084 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Nov 08 01:17:40.000 [warn] Your log may contain sensitive information - you disabled SafeLogging. Don't log unless it serves an important reason. Overwrite the log afterwards.
Nov 08 01:17:40.000 [notice] Parsing GEOIP IPv4 file ..\data\geoip.
Nov 08 01:17:40.000 [notice] Parsing GEOIP IPv6 file ..\data\geoip6.
Nov 08 01:17:40.000 [notice] Bootstrapped 0% (starting): Starting
Nov 08 01:17:42.000 [notice] Starting with guard context "bridges"
Nov 08 01:17:42.000 [notice] Delaying directory fetches: No running bridges
Nov 08 01:17:43.000 [notice] Bridge 'Yann' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address [...]
Nov 08 01:17:45.000 [notice] Bootstrapped 100% (done): Done
0.4.8.13: (crash)
Nov 08 01:22:14.000 [notice] Tor 0.4.8.13 (git-e153e72c01315f86) opening new log file.
Nov 08 01:22:14.685 [notice] We compiled with OpenSSL 300000f0: OpenSSL 3.0.15 3 Sep 2024 and we are running with OpenSSL 300000f0: 3.0.15. These two versions should be binary compatible.
Nov 08 01:22:14.695 [notice] Tor 0.4.8.13 (git-e153e72c01315f86) running on Windows 7 with Libevent 2.1.12-stable, OpenSSL 3.0.15, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Nov 08 01:22:14.695 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Nov 08 01:22:14.701 [notice] Read configuration file "C:\AntiTor\torrc.txt".
Nov 08 01:22:14.703 [warn] Path for CacheDirectory (..\data) is relative and will resolve to C:\AntiTor\data. Is this what you wanted?
Nov 08 01:22:14.703 [warn] Path for DataDirectory (..\data) is relative and will resolve to C:\AntiTor\data. Is this what you wanted?
Nov 08 01:22:14.703 [warn] Path for GeoIPFile (..\data\geoip) is relative and will resolve to C:\AntiTor\data\geoip. Is this what you wanted?
Nov 08 01:22:14.703 [warn] Path for GeoIPv6File (..\data\geoip6) is relative and will resolve to C:\AntiTor\data\geoip6. Is this what you wanted?
Nov 08 01:22:14.704 [notice] Opening Socks listener on 127.0.0.1:9050
Nov 08 01:22:14.705 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
Nov 08 01:22:14.000 [warn] Your log may contain sensitive information - you disabled SafeLogging. Don't log unless it serves an important reason. Overwrite the log afterwards.
Nov 08 01:22:14.000 [notice] Parsing GEOIP IPv4 file ..\data\geoip.
Nov 08 01:22:15.000 [notice] Parsing GEOIP IPv6 file ..\data\geoip6.
Nov 08 01:22:15.000 [notice] Bootstrapped 0% (starting): Starting
Nov 08 01:22:17.000 [notice] Starting with guard context "bridges"
Nov 08 01:22:17.000 [notice] Delaying directory fetches: No running bridges
Nov 08 01:22:18.000 [notice] Bridge 'Yann' has both an IPv4 and an IPv6 address. Will prefer using its IPv6 address
[...]
Nov 08 01:22:18.000 [warn] Managed proxy "pluggable_transports\lyrebird" process terminated with status code 2
Nov 08 01:22:18.000 [err] tor_assertion_failed_: Bug: transports.c:520: proxy_prepare_for_restart: Assertion mp->conf_state == PT_PROTO_COMPLETED failed; aborting. (on Tor 0.4.8.13 e153e72c01315f86)
Nov 08 01:22:18.000 [err] Bug: Tor 0.4.8.13 (git-e153e72c01315f86): Assertion mp->conf_state == PT_PROTO_COMPLETED failed in proxy_prepare_for_restart at transports.c:520: . (Stack trace not available) (on Tor 0.4.8.13 e153e72c01315f86)
I can also provide debug, but oh well they will be large, its not good to send them in messages.
There is also a gitlab anonymous issue from me now, they still not approved my account, so I cant do anything. I need to provide debug logs from both versions.
Now I realize that this is a bad place for this issue. I should’ve created it at The Tor Project / Core / Tor · GitLab, not at The Tor Project / Applications / tor-browser-bundle-testsuite · GitLab, I was confused because of the word “bundle” here. And I still can’t do anything because this issue was created anonymously, oh, why…
Answered in the ticket, but will also post here:
Tor Browser 14.0 drops support for Windows 7 in both Tor Browser itself (i.e. firefox.exe) as well as the pluggable-transports (i.e. lyrebird.exe, snowflake-client.exe, and conjure-client.exe). The firefox.exe requriements are due myriad upstream security improvements which require modern win32 APIs not available before Windows 10. The pluggable-transport requirements are due to updating to a supported version of Go. Google dropped support for Windows 7 a few major versions ago (1.21 I think but don’t quote me on that).
Prior to 14.0, we were using the older version of Go to build lyrebird.exe on Windows (but not snowflake-client.exe as it has a hard dependency on newer Go versions). As part of the Tor Browser 14.0 update, we updated to the most recent Go and are keeping it up-to-date with the latest security updates. So, if you’re on Windows 7, the tor-expert-bundle on the torproject.org website ( Tor Project | Download Tor ) will no longer work for you.
For the next ~6 months or so, we will continue releasing Tor Browser 13.5 for legacy Windows and macOS (since Mozilla is doing likewise for Firefox ESR 115). These builds are not being posted on the main-website, but if you have a previous 13.5 install on a legacy platform, you will continue receiving updates so long as Mozilla is providing ESR security backports.
However, if you are a power-user you can download the tor-expert-bundle package for your platform from the latest in the 13.5.X series (currently 13.5.9) here:
This distribution will be receiving tor.exe updates, but the remaining pluggable-transports will most likely not be getting future feature updates. We will continue releasing this legacy channel for as long as Mozilla maintains ESR 115 (about ~6 more months). So, using this legacy channel is only a short-term solution. We would highly encourage people to either upgrade to a newer version of Windows or (preferably) migrate to an operating system that respects its users. Linux support on legacy platforms is generally pretty good these days, and you can even try with a live usb disk before you install.
Since I can’t upload debug logs directly as files, here they are as links: