Manual test run on Windows arm64 for Tor 0.4.8.10 - Release #2

GeetaSarvadnya commented 4 days ago

`Windows arm64`

Tor Client Updater

[x] 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.
[x] Navigate to brave://components and verify Tor Client Updater (OS) is updated successfully.
[x] Open New Private Window with Tor and confirm that it starts without any errors.
- [x] Navigate to check.torproject.org and verify that tor is working successfully.
- [x] Navigate to brave.com and http://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/ to check if the sites work correctly.
[x] 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

[x] Setup Windows SDK by downloading - https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/
[x] 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.

MadhaviSeelam commented 4 days ago

Verification PASSED using

Brave | 1.67.123 Chromium: 126.0.6478.126 (Official Build) (arm64)
-- | --
Revision | fc7619ef621fe4e6a0fa8b16c718f78ffc97a861
OS | Windows 11 Version 23H2 (Build 22631.3737)

Note: Filed https://github.com/brave/brave-browser/issues/39467 for tor binary information not shown the logs

Launched 1.67.123 Chromium: 126.0.6478.126 using --use-dev-goupdater-url and confirmed the following versions:

tor binary 0.4.8.10
Brave Tor Client Updater (Windows) -Version: 1.0.75
OpenSSL - 3.0.13
Zlib - 1.3.1
Libevent - 2.1.12

Note: Not seeing correct logs

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

brave.com
duckduckgo.com
https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion
check.torproject.org (ensured that hard refreshing gets a new circuit/IP)

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

brave.com --> https://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion
mail.protonmail.com --> https://protonmailrmez3lotccipshtkleegetolb73fuirgj7r4o4vfu7ozyd.onion

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

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

Successfully verified: C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.75\tor-0.4.8.10-win32-brave-2

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

Verified the certificate and ensured that the certificate date is shown correctly

MadhaviSeelam commented 4 days ago

@GeetaSarvadnya @fmarier - Same issue in Win 11 arm64. Not seeing correct logs

GeetaSarvadnya commented 1 day ago

Tor console logs are shown now, please check https://bravesoftware.slack.com/archives/C0YL5KMA8/p1719817342696889?thread_ts=1719509981.321199&cid=C0YL5KMA8.

MadhaviSeelam commented 18 hours ago

Tor console logs are shown with -enable-logging w/o=stderr --use-dev-goupdater-url. QA complete.

Jul 02 08:56:38.462 [notice] Tor 0.4.8.10 running on Windows 8 [or later] with Libevent 2.1.12-stable, OpenSSL 3.0.13, Zlib 1.3.1, Liblzma N/A, Libzstd N/A and Unknown N/A as libc.
Jul 02 08:56:38.463 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jul 02 08:56:38.468 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.75\tor-torrc".
Jul 02 08:56:38.468 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.75\tor-torrc".
Jul 02 08:56:38.469 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.75\<default>. Is this what you wanted?
Jul 02 08:56:38.469 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.75\<default>. Is this what you wanted?
Jul 02 08:56:38.471 [notice] Opening Socks listener on 127.0.0.1:0
Jul 02 08:56:38.471 [notice] Socks listener listening on port 56412.
Jul 02 08:56:38.471 [notice] Opened Socks listener connection (ready) on 127.0.0.1:56412
Jul 02 08:56:38.471 [notice] Opening Control listener on 127.0.0.1:0
Jul 02 08:56:38.471 [notice] Control listener listening on port 56413.
Jul 02 08:56:38.471 [notice] Opened Control listener connection (ready) on 127.0.0.1:56413
Jul 02 08:56:38.000 [notice] Bootstrapped 0% (starting): Starting
Jul 02 08:56:38.000 [notice] Starting with guard context "default"
Jul 02 08:56:38.000 [notice] New control connection opened from 127.0.0.1.
Jul 02 08:56:38.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.75\<default>. Is this what you wanted?
Jul 02 08:56:38.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.75\<default>. Is this what you wanted?
Jul 02 08:56:38.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Jul 02 08:56:38.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.75\<default>. Is this what you wanted?
Jul 02 08:56:38.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.75\<default>. Is this what you wanted?
Jul 02 08:56:40.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Jul 02 08:56:41.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Jul 02 08:56:41.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Jul 02 08:56:41.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Jul 02 08:56:42.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Jul 02 08:56:42.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Jul 02 08:56:44.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Jul 02 08:56:44.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Jul 02 08:56:45.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Jul 02 08:56:45.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Jul 02 08:56:45.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7300, 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.)
Jul 02 08:56:47.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Jul 02 08:56:51.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Jul 02 08:56:57.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
Jul 02 08:56:57.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors
Jul 02 08:56:57.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
Jul 02 08:56:57.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Jul 02 08:56:58.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Jul 02 08:56:58.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Jul 02 08:57:00.000 [notice] Bootstrapped 100% (done): Done

brave / brave-browser