• Jesse McKenna's avatar
    Use consistent DLL to detect Application Verifier · fd8fe93c
    Jesse McKenna authored
    To detect whether Application Verifier is running,
    sandbox/win/src/target_interceptions.cc checks if vrfcore.dll is loaded,
    while sandbox/win/src/handle_closer_agent.cc checks for verifier.dll.
    
    This change makes both use verifier.dll, to be consistent and remove any
    confusion around whether these two are checking for the same thing (they
    are).
    
          Open Application Verifier
          File > Add Application > chrome.exe (any chrome.exe binary works)
          Under 'Tests', uncheck everything but Basics > Handles, then Save
          Run chrome.exe with this change; it works normally
            (on versions without lines 176-177, no pages will load)
          Return to Application Verifier
          Right-click chrome.exe > Delete Application, then Save
            (so Chrome runs normally again)
    
    Test: Manual
    Change-Id: If97a1115373c394f0cbbf1d31d3ca7b60549bbee
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1776781
    Commit-Queue: Jesse McKenna <jessemckenna@google.com>
    Reviewed-by: default avatarGreg Thompson <grt@chromium.org>
    Reviewed-by: default avatarWill Harris <wfh@chromium.org>
    Reviewed-by: default avatarBruce Dawson <brucedawson@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#700323}
    fd8fe93c
win_util.cc 29.5 KB