This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 972
Update windows tor binaries to 0.3.3.7 #14463
Labels
feature/tor
needs-info
Another team member needs information from the PR/issue opener.
OS/Windows
QA/checked-Win64
QA/test-plan-specified
release-notes/exclude
Milestone
Comments
11 tasks
diracdeltas
pushed a commit
that referenced
this issue
Jun 22, 2018
* Adapt package_tor.js to the mingw build of tor. fix #14463 Auditors: @jumde @diracdeltas Test Plan: 1. Install Brave on Windows. 2. Launch it. 3. Browse around in a tab with Tor enabled. * No more need for unzip. * Updating hash for windows binary * update package-lock
Fixed with #14507 |
diracdeltas
pushed a commit
that referenced
this issue
Jun 22, 2018
* Adapt package_tor.js to the mingw build of tor. fix #14463 Auditors: @jumde @diracdeltas Test Plan: 1. Install Brave on Windows. 2. Launch it. 3. Browse around in a tab with Tor enabled. * No more need for unzip. * Updating hash for windows binary * update package-lock
bsclifton
pushed a commit
that referenced
this issue
Jun 23, 2018
* Adapt package_tor.js to the mingw build of tor. fix #14463 Auditors: @jumde @diracdeltas Test Plan: 1. Install Brave on Windows. 2. Launch it. 3. Browse around in a tab with Tor enabled. * No more need for unzip. * Updating hash for windows binary * update package-lock
kjozwiak
added
needs-info
Another team member needs information from the PR/issue opener.
QA/test-plan-required
labels
Jun 25, 2018
@jumde @diracdeltas is there a way to check which version is being used on Windows? It seems like running Brave through the command prompt doesn't output as much information as macOS & Linux does. Example: |
@kjozwiak binaries shows in tor log. Looks good on Windows Verified on Windows 10 x64 using
|
srirambv
added
QA/checked-Win64
QA/test-plan-specified
and removed
QA/test-plan-required
labels
Jun 25, 2018
bsclifton
pushed a commit
that referenced
this issue
Jun 25, 2018
* Adapt package_tor.js to the mingw build of tor. fix #14463 Auditors: @jumde @diracdeltas Test Plan: 1. Install Brave on Windows. 2. Launch it. 3. Browse around in a tab with Tor enabled. * No more need for unzip. * Updating hash for windows binary * update package-lock
Thanks @srirambv 👍 Probably should have checked the logs first ;) |
bsclifton
pushed a commit
that referenced
this issue
Jun 26, 2018
* Adapt package_tor.js to the mingw build of tor. fix #14463 Auditors: @jumde @diracdeltas Test Plan: 1. Install Brave on Windows. 2. Launch it. 3. Browse around in a tab with Tor enabled. * No more need for unzip. * Updating hash for windows binary * update package-lock
bsclifton
pushed a commit
that referenced
this issue
Jun 27, 2018
* Adapt package_tor.js to the mingw build of tor. fix #14463 Auditors: @jumde @diracdeltas Test Plan: 1. Install Brave on Windows. 2. Launch it. 3. Browse around in a tab with Tor enabled. * No more need for unzip. * Updating hash for windows binary * update package-lock
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
feature/tor
needs-info
Another team member needs information from the PR/issue opener.
OS/Windows
QA/checked-Win64
QA/test-plan-specified
release-notes/exclude
#Test plan
%AppData%\Roaming\brave\tor\data\tor.log
https://blog.torproject.org/tor-0337-released
The text was updated successfully, but these errors were encountered: