-
Notifications
You must be signed in to change notification settings - Fork 13
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
Added 50/50 experiment for binary name spoofing in GPU process. #578
Conversation
…leFileNamePatch feature. ]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 Merging so QA can run through the above on main
(staging) before pushing the above via production
.
Hmmm looks like we'll have issues with |
|
Example |
Example |
Example |
---|---|---|
![]() |
![]() |
![]() |
ModuleFileNamePatchStudy:Default
Verification PASSED on Win 11 x64
using the following build(s):
Brave | 1.52.37 Chromium: 112.0.5615.49 (Official Build) nightly (64-bit)
-- | --
Revision | bd2a7bcb881c11e8cfe3078709382934e3916914-refs/branch-heads/5615@{#936}
OS | Windows 11 Version 22H2 (Build 22621.1413)
Basically used the STR/Cases outlined via brave/brave-core#17671 (comment).
- launched
1.52.37 Chromium: 112.0.5615.49
using the terminal/CLI switchbrave.exe --enable-logging=stderr --variations-server-url=https://variations.bravesoftware.com/seed
- ensured that
ModuleFileNamePatchStudy
wasn't being displayed viabrave://version
- restarted the browser and ensured that
ModuleFileNamePatchStudy:Default
viabrave://version
- checked
brave://gpu
and ensured that all the paths underExecutable path
are pointing tobrave.exe
GetModuleFileNameExA = C:\Program Files\BraveSoftware\Brave-Browser-Nightly\Application\brave.exe
GetModuleFileNameExW = C:\Program Files\BraveSoftware\Brave-Browser-Nightly\Application\brave.exe
GetModuleFileNameA = C:\Program Files\BraveSoftware\Brave-Browser-Nightly\Application\brave.exe
GetModuleFileNameW = C:\Program Files\BraveSoftware\Brave-Browser-Nightly\Application\brave.exe
Example |
Example |
Example |
---|---|---|
![]() |
![]() |
![]() |
Desktop
verifications on Beta
Win 11 x64
Test Cases
ModuleFileNamePatchStudy:Enabled
Verification PASSED on Win 11 x64
using the following build(s):
Brave | 1.51.94 Chromium: 112.0.5615.121 (Official Build) beta (64-bit)
-- | --
Revision | 39cc4e45904ae9f1741c4fbaa866e629c96f2268-refs/branch-heads/5615_51@{#8}
OS | Windows 11 Version 22H2 (Build 22621.1555)
Basically used the STR/Cases outlined via brave/brave-core#17671 (comment).
- launched
1.51.94 Chromium: 112.0.5615.121
using the terminal/CLI switchbrave.exe --enable-logging=stderr --variations-server-url=https://variations.bravesoftware.com/seed
- ensured that
ModuleFileNamePatchStudy
wasn't being displayed viabrave://version
- restarted the browser and ensured that
ModuleFileNamePatchStudy:Enabled
viabrave://version
- checked
brave://gpu
and ensured that all the paths underExecutable path
are pointing tochrome.exe
GetModuleFileNameExA = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\chrome.exe GetModuleFileNameExW = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\chrome.exe
GetModuleFileNameA = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\chrome.exe
GetModuleFileNameW = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\chrome.exe
Example |
Example |
Example |
---|---|---|
![]() |
![]() |
![]() |
ModuleFileNamePatchStudy:Default
Verification PASSED on Win 11 x64
using the following build(s):
Brave | 1.51.94 Chromium: 112.0.5615.121 (Official Build) beta (64-bit)
-- | --
Revision | 39cc4e45904ae9f1741c4fbaa866e629c96f2268-refs/branch-heads/5615_51@{#8}
OS | Windows 11 Version 22H2 (Build 22621.1555)
Basically used the STR/Cases outlined via brave/brave-core#17671 (comment).
- launched
1.51.94 Chromium: 112.0.5615.121
using the terminal/CLI switchbrave.exe --enable-logging=stderr --variations-server-url=https://variations.bravesoftware.com/seed
- ensured that
ModuleFileNamePatchStudy
wasn't being displayed viabrave://version
- restarted the browser and ensured that
ModuleFileNamePatchStudy:Default
viabrave://version
- checked
brave://gpu
and ensured that all the paths underExecutable path
are pointing tobrave.exe
GetModuleFileNameExA = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\brave.exe
GetModuleFileNameExW = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\brave.exe
GetModuleFileNameA = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\brave.exe
GetModuleFileNameW = C:\Program Files\BraveSoftware\Brave-Browser-Beta\Application\brave.exe
Example |
Example |
Example |
---|---|---|
![]() |
![]() |
![]() |
Desktop
verifications on Release
Win 11 x64
Test Cases
ModuleFileNamePatchStudy
(shouldn't bet appearing due to not meeting channel requirements)
Verification PASSED on Win 11 x64
using the following build(s):
Brave | 1.50.119 Chromium: 112.0.5615.121 (Official Build) (64-bit)
-- | --
Revision | 39cc4e45904ae9f1741c4fbaa866e629c96f2268-refs/branch-heads/5615_51@{#8}
OS | Windows 11 Version 22H2 (Build 22621.1555)
Basically used the STR/Cases outlined via brave/brave-core#17671 (comment).
- launched
1.50.119 Chromium: 112.0.5615.121
using the terminal/CLI switchbrave.exe --enable-logging=stderr --variations-server-url=https://variations.bravesoftware.com/seed
- ensured that
ModuleFileNamePatchStudy
wasn't being displayed viabrave://version
- restarted the browser and ensured that
ModuleFileNamePatchStudy
isn't appearing underbrave://version
- checked
brave://gpu
and ensured that all the paths underExecutable path
are pointing tobrave.exe
Resolves #579
ModuleFileNamePatch feature.