Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual test run on Windows x64 & x86 for Tor 0.4.8.14 - Release #1 #43908

Open
16 of 24 tasks
GeetaSarvadnya opened this issue Feb 12, 2025 · 2 comments
Open
16 of 24 tasks

Comments

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Feb 12, 2025

Windows 11 x64

Tor Client Updater

  • For development go-update-server. Run brave-browser with --user-data-dir=component-dev --use-dev-goupdater-url (These flags are only available in v1.7.x). Once the crx is pushed to production run without these flags.
  • Navigate to brave://components and verify Tor Client Updater (OS) is updated successfully.
  • Open New Private Window with Tor and confirm that it starts without any errors.
    • Navigate to check.torproject.org and verify that tor is working successfully.
    • Navigate to brave.com and http://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/ to check if the sites work correctly.
  • Load brave.com and mail.protonmail.com in a regular Window/Tab and ensure that clicking the Tor button in the URL bar correctly launches a Tor window and opens the appropriate .onion website.

Windows

  • Setup Windows SDK by downloading - https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
  • Run "C:\Program Files (x86)\Windows Kits\10\bin\x86\signtool.exe" verify /pa "C:\Users\<user>\AppData\Local\BraveSoftware\Brave-Browser-<channel>\User Data\cpoalefficncklhjfpglfiplenlpccdb\<version>\tor-<version-tor>-win-brave-<version-brave>.exe" to verify if the signature of the binary is correct.

Windows 10 x64

Tor Client Updater

  • For development go-update-server. Run brave-browser with --user-data-dir=component-dev --use-dev-goupdater-url (These flags are only available in v1.7.x). Once the crx is pushed to production run without these flags.
  • Navigate to brave://components and verify Tor Client Updater (OS) is updated successfully.
  • Open New Private Window with Tor and confirm that it starts without any errors.
    • Navigate to check.torproject.org and verify that tor is working successfully.
    • Navigate to brave.com and http://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/ to check if the sites work correctly.
  • Load brave.com and mail.protonmail.com in a regular Window/Tab and ensure that clicking the Tor button in the URL bar correctly launches a Tor window and opens the appropriate .onion website.

Windows

  • Setup Windows SDK by downloading - https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
  • Run "C:\Program Files (x86)\Windows Kits\10\bin\x86\signtool.exe" verify /pa "C:\Users\<user>\AppData\Local\BraveSoftware\Brave-Browser-<channel>\User Data\cpoalefficncklhjfpglfiplenlpccdb\<version>\tor-<version-tor>-win-brave-<version-brave>.exe" to verify if the signature of the binary is correct.

Windows 10 x86

Tor Client Updater

  • For development go-update-server. Run brave-browser with --user-data-dir=component-dev --use-dev-goupdater-url (These flags are only available in v1.7.x). Once the crx is pushed to production run without these flags.
  • Navigate to brave://components and verify Tor Client Updater (OS) is updated successfully.
  • Open New Private Window with Tor and confirm that it starts without any errors.
    • Navigate to check.torproject.org and verify that tor is working successfully.
    • Navigate to brave.com and http://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/ to check if the sites work correctly.
  • Load brave.com and mail.protonmail.com in a regular Window/Tab and ensure that clicking the Tor button in the URL bar correctly launches a Tor window and opens the appropriate .onion website.

Windows

  • Setup Windows SDK by downloading - https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
  • Run "C:\Program Files (x86)\Windows Kits\10\bin\x86\signtool.exe" verify /pa "C:\Users\<user>\AppData\Local\BraveSoftware\Brave-Browser-<channel>\User Data\cpoalefficncklhjfpglfiplenlpccdb\<version>\tor-<version-tor>-win-brave-<version-brave>.exe" to verify if the signature of the binary is correct.
@GeetaSarvadnya
Copy link
Author

GeetaSarvadnya commented Feb 12, 2025

Verification PASSED on

Brave | 1.75.176 Chromium: 133.0.6943.54 (Official Build) (64-bit)
-- | --
Revision | e6801717df1140ddca5688337974f103e95ed307
OS | Windows 10 Version 22H2 (Build 19045.5371)

Launched 1.75.176 Chromium: 133.0.6943.54 using brave.exe --enable-logging --use-dev-goupdater-url and confirmed the following versions:

  • tor binary 0.4.8.14
  • Brave Tor Client Updater (Windows) -Version: 1.0.77
  • OpenSSL - 3.4.1
  • Zlib - 1.3.1
  • Libevent - 2.1.12-stable

Image

Feb 12 11:49:49.239 [notice] Tor 0.4.8.14 running on Windows 8 [or later] with Libevent 2.1.12-stable, OpenSSL 3.4.1, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Feb 12 11:49:49.239 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 12 11:49:49.247 [notice] Read configuration file "C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-torrc".
Feb 12 11:49:49.248 [notice] Read configuration file "C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-torrc".
Feb 12 11:49:49.249 [warn] Path for GeoIPFile (<default>) is relative and will resolve to 
Feb 12 11:49:49.252 [notice] Opening Socks listener on 127.0.0.1:0
Feb 12 11:49:49.252 [notice] Socks listener listening on port 63792.
Feb 12 11:49:49.252 [notice] Opened Socks listener connection (ready) on 127.0.0.1:63792
Feb 12 11:49:49.252 [notice] Opening Control listener on 127.0.0.1:0
Feb 12 11:49:49.253 [notice] Control listener listening on port 63793.
Feb 12 11:49:49.253 [notice] Opened Control listener connection (ready) on 127.0.0.1:63793
Feb 12 11:49:49.000 [notice] Bootstrapped 0% (starting): Starting
Feb 12 11:49:49.000 [notice] Starting with guard context "default"
Feb 12 11:49:49.000 [notice] New control connection opened from 127.0.0.1.
Feb 12 11:49:49.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 12 11:49:49.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 12 11:49:50.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 12 11:49:50.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Feb 12 11:49:50.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Feb 12 11:49:50.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Feb 12 11:49:59.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Feb 12 11:49:59.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Feb 12 11:50:00.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Feb 12 11:50:00.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Feb 12 11:50:00.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/8092, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Feb 12 11:50:01.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Feb 12 11:50:09.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Feb 12 11:50:10.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
Feb 12 11:50:10.000 [notice] Bootstrapped 60% (loading_descriptors): Loading relay descriptors
Feb 12 11:50:21.000 [notice] Bootstrapped 67% (loading_descriptors): Loading relay descriptors
Feb 12 11:50:23.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 12 11:50:23.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 12 11:50:23.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 12 11:50:24.000 [notice] Bootstrapped 100% (done): Done

Ensured that you can open the following domains in a Tor window without issues:

Confirmed the following sites opened via "Open in Tor" button and navigated to .onion URL:

Ensured that the tor binary was correctly signed using signtool.exe:

c:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64>BraveSign.exe verify /pa "c:\Users\Dell\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-0.4.8.14-win32-brave-0"
File: c:\Users\Dell\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-0.4.8.14-win32-brave-0
Index  Algorithm  Timestamp
========================================
0      sha256     Authenticode

Successfully verified: c:\Users\Dell\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-0.4.8.14-win32-brave-0

c:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64>

@MadhaviSeelam
Copy link

MadhaviSeelam commented Feb 12, 2025

Verification PASSED using

Brave | 1.75.175 Chromium: 133.0.6943.54 (Official Build) (64-bit)
-- | --
Revision | 8e82be95a27b2e442e0099307c0c8ad6d12adcf0
OS | Windows 11 Version 24H2 (Build 26100.2894)

Launched 1.75.175 Chromium: 133.0.6943.54 (Official Build) (64-bit) using brave.exe --enable-logging --use-dev-goupdater-url and confirmed the following versions:

  • tor binary 0.4.8.14
  • Brave Tor Client Updater (Windows) - Version: 1.0.77
  • OpenSSL - 3.4.1
  • Zlib - 1.3.1
  • Libevent - 2.1.12-stable

Image

Feb 12 09:12:02.031 [notice] Tor 0.4.8.14 running on Windows 8 [or later] with Libevent 2.1.12-stable, OpenSSL 3.4.1, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Feb 12 09:12:02.031 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Feb 12 09:12:02.031 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-torrc".
Feb 12 09:12:02.031 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-torrc".
Feb 12 09:12:02.031 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\<default>. Is this what you wanted?
Feb 12 09:12:02.031 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\<default>. Is this what you wanted?
Feb 12 09:12:02.031 [notice] Opening Socks listener on 127.0.0.1:0
Feb 12 09:12:02.031 [notice] Socks listener listening on port 62517.
Feb 12 09:12:02.031 [notice] Opened Socks listener connection (ready) on 127.0.0.1:62517
Feb 12 09:12:02.031 [notice] Opening Control listener on 127.0.0.1:0
Feb 12 09:12:02.031 [notice] Control listener listening on port 62518.
Feb 12 09:12:02.031 [notice] Opened Control listener connection (ready) on 127.0.0.1:62518
Feb 12 09:12:02.000 [notice] Bootstrapped 0% (starting): Starting
Feb 12 09:12:02.000 [notice] Starting with guard context "default"
Feb 12 09:12:02.000 [notice] New control connection opened from 127.0.0.1.
Feb 12 09:12:02.000 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\<default>. Is this what you wanted?
Feb 12 09:12:02.000 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\<default>. Is this what you wanted?
Feb 12 09:12:02.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 12 09:12:02.000 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\<default>. Is this what you wanted?
Feb 12 09:12:02.000 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\<default>. Is this what you wanted?
Feb 12 09:12:02.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 12 09:12:02.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 12 09:12:02.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 12 09:12:02.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Feb 12 09:12:02.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Feb 12 09:12:02.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Feb 12 09:12:02.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Feb 12 09:12:02.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Feb 12 09:12:02.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Feb 12 09:12:02.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Feb 12 09:12:02.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/8074, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
Feb 12 09:12:04.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Feb 12 09:12:05.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Feb 12 09:12:09.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
Feb 12 09:12:09.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
Feb 12 09:12:10.000 [notice] Bootstrapped 71% (loading_descriptors): Loading relay descriptors
Feb 12 09:12:10.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 12 09:12:11.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 12 09:12:11.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 12 09:12:11.000 [notice] Bootstrapped 100% (done): Done

Ensured that you can open the following domains in a Tor window without issues:

Confirmed the following sites opened via "Open in Tor" button and navigated to .onion URL:

Ensured that the tor binary was correctly signed using signtool.exe:

C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64>BraveSign.exe verify /pa "C:\Users\mseel\AppData\Local\Brave
Software\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-0.4.8.14-win32-brave-0"
File: C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-0.4.8.14-win32-brave-0
Index  Algorithm  Timestamp
========================================
0      sha256     Authenticode

Successfully verified: C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.77\tor-0.4.8.14-win32-brave-0

C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment