debugging_gpu_related_code.md explains how to use a Chrome command-line
switch which has been used for arbitrary code execution. Windows
Defender therefore treats it as malware. This means that some Windows
Chromium developers will get anti-virus warnings (with mandatory
quarantining of the file). If Chrome is in a directory that is
excluded from scanning then they will avoid warnings but will hit
problems if they try to use Windows backup.
This is all very silly since there is no way - short of manually
following the steps, modify to be malicious - to activate this payload.
Windows Defender even complains about the file created by this:
> echo --no-sandbox --gpu-launcher="x" >foo.txt
But, sometimes it's not worth arguing.
This also fixes a typo.
R=kainino@chromium.org
BUG=851562
Change-Id: I85403a1cb1667f45784684179927119058608d40
Reviewed-on: https://chromium-review.googlesource.com/1096311
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Kai Ninomiya <kainino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#566245}
f17419f416