Manual test run on Linux for Tor 0.4.7.13 - Release #1

[GeetaSarvadnya]

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.

Linux

• Navigate to <user-data-dir>/biahpgbdmdkfgndcmfiipgcebobojjkp
• Run ldd tor-<version-tor>-linux-brave-<version-brave> to confirm tor client is a static binary

[GeetaSarvadnya]

Quick note: The Tor daemon is updated from 0.4.7.11 -> 0.4.7.13, OpenSSL is updated from 1.1.1s -> 1.1.1t However, the Zlib vesrion - 1.2.13 remained same

[btlechowski]

Verification passed on

Brave	1.48.158 Chromium: 110.0.5481.77 (Official Build) (64-bit)
Revision	65ed616c6e8ee3fe0ad64fe83796c020644d42af-refs/branch-heads/5481@{#839}
OS	Ubuntu 18.04 LTS

Feb 09 12:51:05.880 [notice] Tor 0.4.7.13 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1t, Zlib 1.2.13, Liblzma N/A, Libzstd N/A and Glibc 2.35 as libc.