Closed Bug 1801772 Opened 3 years ago Closed 11 months ago

MS Defender AV exclusions aren't setup when running `mach bootstrap`

Categories

(Firefox Build System :: Bootstrap Configuration, task, P3)

task

Tracking

(Not tracked)

RESOLVED FIXED

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.

(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, ~/.mozbuild is added to the exclusion list, but it should respect MOZBUILD_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.

Severity: -- → S3
Priority: -- → P3

This was done in bug 1963696.

Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.