Closed srirambv closed 7 months ago
Verification PASSED on
Brave | 1.63.165 Chromium: 122.0.6261.94 (Official Build) (64-bit)
-- | --
Revision | fed0fcc915f6d9e1db871202f0304c8d582a73de
OS | Windows 10 Version 22H2 (Build 19045.4046)
Launched 1.63.165 Chromium: 122.0.6261.94
using --use-dev-goupdater-url
and confirmed the following versions:
tor
binary 0.4.8.10
Brave Tor Client Updater (Windows) -Version: 1.0.72
OpenSSL
- 3.0.13
Zlib
- 1.3.1
Libevent
- 2.1.12-stable
Feb 29 12:50:27.161 [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.
Feb 29 12:50:27.161 [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 29 12:50:27.168 [notice] Read configuration file "C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-torrc".
Feb 29 12:50:27.169 [notice] Read configuration file "C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-torrc".
Feb 29 12:50:27.170 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 12:50:27.170 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 12:50:27.172 [notice] Opening Socks listener on 127.0.0.1:0
Feb 29 12:50:27.173 [notice] Socks listener listening on port 54848.
Feb 29 12:50:27.173 [notice] Opened Socks listener connection (ready) on 127.0.0.1:54848
Feb 29 12:50:27.173 [notice] Opening Control listener on 127.0.0.1:0
Feb 29 12:50:27.173 [notice] Control listener listening on port 54849.
Feb 29 12:50:27.173 [notice] Opened Control listener connection (ready) on 127.0.0.1:54849
[22548:27956:0229/125027.175:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[22548:27956:0229/125027.175:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[22548:27956:0229/125027.175:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[22548:27956:0229/125027.179:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[22548:27956:0229/125027.180:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
Feb 29 12:50:27.000 [notice] Bootstrapped 0% (starting): Starting
Feb 29 12:50:27.000 [notice] Starting with guard context "default"
Feb 29 12:50:27.000 [notice] New control connection opened from 127.0.0.1.
Feb 29 12:50:27.000 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 12:50:27.000 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 12:50:27.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 29 12:50:27.000 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 12:50:27.000 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\DELL\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
[22548:11632:0229/125027.281:INFO:CONSOLE(0)] "Slow network is detected. See https://www.chromestatus.com/feature/5636954674692096 for more details. Fallback font will be used while loading: chrome://resources/brave/fonts/third_party/poppins/Poppins_700_normal_latin_v20.woff2", source: chrome://newtab/ (0)
Feb 29 12:50:27.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 29 12:50:27.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 29 12:50:28.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 29 12:50:28.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Feb 29 12:50:29.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Feb 29 12:50:29.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Feb 29 12:50:34.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Feb 29 12:50:34.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Feb 29 12:50:35.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Feb 29 12:50:35.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Feb 29 12:50:35.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7544, 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 29 12:50:36.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Feb 29 12:50:39.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Feb 29 12:50:59.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
Feb 29 12:51:00.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
Feb 29 12:51:00.000 [notice] Bootstrapped 71% (loading_descriptors): Loading relay descriptors
Feb 29 12:51:00.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 29 12:51:01.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 29 12:51:01.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 29 12:51:02.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.72\tor-0.4.8.10-win32-brave-1"
File: c:\Users\Dell\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1
Index Algorithm Timestamp
========================================
0 sha256 Authenticode
Successfully verified: c:\Users\Dell\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1
c:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64>
Verification PASSED
using
Brave | 1.63.165 Chromium: 122.0.6261.94 (Official Build) (64-bit)
-- | --
Revision | fed0fcc915f6d9e1db871202f0304c8d582a73de
OS | Windows 11 Version 23H2 (Build 22631.3155)
Launched 1.63.165 Chromium: 122.0.6261.94
using --use-dev-goupdater-url
and confirmed the following versions:
Tor
binary 0.4.8.10
Brave Tor Client Updater (Windows)
-Version: 1.0.72
OpenSSL
- 3.0.13
Zlib
- 1.3.1
Libevent
- 2.1.12-stable
Feb 29 09:41:17.549 [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.
Feb 29 09:41:17.549 [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 29 09:41:17.549 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-torrc".
Feb 29 09:41:17.550 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-torrc".
Feb 29 09:41:17.550 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 09:41:17.550 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 09:41:17.552 [notice] Opening Socks listener on 127.0.0.1:0
Feb 29 09:41:17.552 [notice] Socks listener listening on port 61916.
Feb 29 09:41:17.552 [notice] Opened Socks listener connection (ready) on 127.0.0.1:61916
Feb 29 09:41:17.552 [notice] Opening Control listener on 127.0.0.1:0
Feb 29 09:41:17.552 [notice] Control listener listening on port 61917.
Feb 29 09:41:17.552 [notice] Opened Control listener connection (ready) on 127.0.0.1:61917
[12128:29276:0229/094117.553:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[12128:29276:0229/094117.553:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[12128:29276:0229/094117.555:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[12128:29276:0229/094117.555:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[12128:29276:0229/094117.555:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
Feb 29 09:41:17.000 [notice] Bootstrapped 0% (starting): Starting
Feb 29 09:41:17.000 [notice] Starting with guard context "default"
Feb 29 09:41:17.000 [notice] New control connection opened from 127.0.0.1.
Feb 29 09:41:17.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.72\<default>. Is this what you wanted?
Feb 29 09:41:17.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.72\<default>. Is this what you wanted?
Feb 29 09:41:17.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 29 09:41:17.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.72\<default>. Is this what you wanted?
Feb 29 09:41:17.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.72\<default>. Is this what you wanted?
Feb 29 09:41:18.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 29 09:41:18.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 29 09:41:19.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 29 09:41:19.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Feb 29 09:41:19.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Feb 29 09:41:19.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Feb 29 09:41:21.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Feb 29 09:41:21.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Feb 29 09:41:21.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Feb 29 09:41:21.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Feb 29 09:41:21.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7521, 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 29 09:41:22.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Feb 29 09:41:37.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Feb 29 09:41:53.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
Feb 29 09:41:53.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
Feb 29 09:41:53.000 [notice] Bootstrapped 71% (loading_descriptors): Loading relay descriptors
Feb 29 09:41:53.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 29 09:41:53.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 29 09:41:53.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 29 09:41:54.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.22621.0\x64>BraveSign.exe verify /pa "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1"
File: C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1
Index Algorithm Timestamp
========================================
0 sha256 Authenticode
Successfully verified: C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1
C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64>
Verification PASSED
using
Brave | 1.63.165 Chromium: 122.0.6261.94 (Official Build) (arm64)
-- | --
Revision | fed0fcc915f6d9e1db871202f0304c8d582a73de
OS | Windows 11 Version 23H2 (Build 22631.3155)
Launched 1.63.165 Chromium: 122.0.6261.94 (Official Build) (arm64)
using --use-dev-goupdater-url and confirmed the following versions:
Tor
binary 0.4.8.10
Brave Tor Client Updater (Windows)
-Version: 1.0.72
OpenSSL
- 3.0.13
Zlib
- 1.3.1
Libevent
- 2.1.12-stable
Feb 29 10:41:09.080 [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.
Feb 29 10:41:09.080 [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 29 10:41:09.080 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-torrc".
Feb 29 10:41:09.080 [notice] Read configuration file "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-torrc".
Feb 29 10:41:09.099 [warn] Path for GeoIPFile (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 10:41:09.099 [warn] Path for GeoIPv6File (<default>) is relative and will resolve to C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\<default>. Is this what you wanted?
Feb 29 10:41:09.099 [notice] Opening Socks listener on 127.0.0.1:0
Feb 29 10:41:09.099 [notice] Socks listener listening on port 50947.
Feb 29 10:41:09.099 [notice] Opened Socks listener connection (ready) on 127.0.0.1:50947
Feb 29 10:41:09.099 [notice] Opening Control listener on 127.0.0.1:0
Feb 29 10:41:09.099 [notice] Control listener listening on port 50948.
Feb 29 10:41:09.099 [notice] Opened Control listener connection (ready) on 127.0.0.1:50948
[18660:18764:0229/104109.112:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[18660:18764:0229/104109.112:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[18660:18764:0229/104109.112:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[18660:18764:0229/104109.112:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[18660:18764:0229/104109.112:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
[18660:18764:0229/104109.112:INFO:tor_file_watcher.cc(183)] tor: failed to open control auth cookie
Feb 29 10:41:09.000 [notice] Bootstrapped 0% (starting): Starting
Feb 29 10:41:09.000 [notice] Starting with guard context "default"
Feb 29 10:41:09.000 [notice] New control connection opened from 127.0.0.1.
Feb 29 10:41:09.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.72\<default>. Is this what you wanted?
Feb 29 10:41:09.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.72\<default>. Is this what you wanted?
Feb 29 10:41:09.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Feb 29 10:41:09.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.72\<default>. Is this what you wanted?
Feb 29 10:41:09.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.72\<default>. Is this what you wanted?
Feb 29 10:41:09.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Feb 29 10:41:09.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
Feb 29 10:41:09.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Feb 29 10:41:09.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
Feb 29 10:41:09.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
Feb 29 10:41:10.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
Feb 29 10:41:10.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
Feb 29 10:41:11.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
Feb 29 10:41:11.000 [notice] The current consensus has no exit nodes. Tor can only build internal paths, such as paths to onion services.
Feb 29 10:41:11.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
Feb 29 10:41:11.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/7467, 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 29 10:41:12.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
Feb 29 10:41:14.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
Feb 29 10:41:17.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
Feb 29 10:41:17.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors
Feb 29 10:41:17.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
Feb 29 10:41:18.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Feb 29 10:41:18.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Feb 29 10:41:18.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
Feb 29 10:41:19.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.22621.0\arm64>BraveSign.exe verify /pa "C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1"
File: C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1
Index Algorithm Timestamp
========================================
0 sha256 Authenticode
Successfully verified: C:\Users\mseel\AppData\Local\BraveSoftware\Brave-Browser\User Data\cpoalefficncklhjfpglfiplenlpccdb\1.0.72\tor-0.4.8.10-win32-brave-1
C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\arm64>
Win 10 x86
- PASSEDVerification PASSED on Win 10 x86
using the following build:
Brave | 1.63.165 Chromium: 122.0.6261.94 (Official Build) (32-bit)
-- | --
Revision | fed0fcc915f6d9e1db871202f0304c8d582a73de
OS | Windows 10 Version 22H2 (Build 19045.4123)
Windows 11 x64
Tor Client Updater
--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.brave://components
and verifyTor Client Updater (OS)
is updated successfully.New Private Window with Tor
and confirm that it starts without any errors.check.torproject.org
and verify that tor is working successfully.brave.com
andhttp://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/
to check if the sites work correctly.brave.com
andmail.protonmail.com
in a regular Window/Tab and ensure that clicking theTor
button in the URL bar correctly launches a Tor window and opens the appropriate.onion
website.Windows
"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
--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.brave://components
and verifyTor Client Updater (OS)
is updated successfully.New Private Window with Tor
and confirm that it starts without any errors.check.torproject.org
and verify that tor is working successfully.brave.com
andhttp://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/
to check if the sites work correctly.brave.com
andmail.protonmail.com
in a regular Window/Tab and ensure that clicking theTor
button in the URL bar correctly launches a Tor window and opens the appropriate.onion
website.Windows
"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
--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.brave://components
and verifyTor Client Updater (OS)
is updated successfully.New Private Window with Tor
and confirm that it starts without any errors.check.torproject.org
and verify that tor is working successfully.brave.com
andhttp://brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion/
to check if the sites work correctly.brave.com
andmail.protonmail.com
in a regular Window/Tab and ensure that clicking theTor
button in the URL bar correctly launches a Tor window and opens the appropriate.onion
website.Windows
"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.