MS Defender AV exclusions aren't setup when running `mach bootstrap`
Categories
(Firefox Build System :: Bootstrap Configuration, task, P3)
Tracking
(Not tracked)
People
(Reporter: glandium, Unassigned)
References
Details
Bug 1276019 added MS Defender AV exclusions, but it did so in the standalone bootstrap (for it to work on the initial clone too), but we should also add them for people who already have a clone and run mach bootstrap.
Tangentially, ~/.mozbuild is added to the exclusion list, but it should respect MOZBUILD_STATE_PATH.
Comment 1•3 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #0)
Bug 1276019 added MS Defender AV exclusions, but it did so in the standalone bootstrap (for it to work on the initial clone too), but we should also add them for people who already have a clone and run
mach bootstrap.Tangentially,
~/.mozbuildis added to the exclusion list, but it should respectMOZBUILD_STATE_PATH.
I think that would cause a Windows UAC prompt for Powershell every time you run ./mach bootstrap (Since I think we'd need an Admin Powershell to even check what's on the AV exclusions list) which would be a bit annoying. I'd be more open to adding it to ./mach doctor instead.
Updated•3 years ago
|
Comment 2•11 months ago
|
||
This was done in bug 1963696.
Description
•