Closed
Bug 1925425
Opened 1 year ago
Closed 1 year ago
Remove the -allow-content-analysis command line flag in Release/ESR
Categories
(Firefox :: Data Loss Prevention, enhancement)
Firefox
Data Loss Prevention
Tracking
()
RESOLVED
FIXED
134 Branch
| Tracking | Status | |
|---|---|---|
| firefox134 | --- | fixed |
People
(Reporter: haik, Assigned: handyman)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Remove the command line flag -allow-content-analysis in Release/ESR to limit enabling content analysis to configurations where an enterprise policy has been configured. Using an enterprise policy has always been the intended way to enable the content analysis SDK support, but the command line flag was provided for development and testing purposes.
| Assignee | ||
Comment 1•1 year ago
|
||
(Also note there is intentionally no single variable covering Beta, as late Beta becomes/is Release.)
We can gate this on nightly/early-beta, but that's it. IDK what this would do to current testing but I think this has been used only for local dev, so that would be ok.
| Assignee | ||
Comment 2•1 year ago
|
||
We use the command line flag for development and local testing. We would like
to allow it in all betas, but late betas are release-candidates, so this will
prevents that as well.
Updated•1 year ago
|
Assignee: nobody → davidp99
Status: NEW → ASSIGNED
Updated•1 year ago
|
Attachment #9435233 -
Attachment description: Bug 1925425: Do not consider -allow-content-analysis command line flag in late beta/release/esr r=#dlp-reviewers!,haik! → Bug 1925425: Only consider -allow-content-analysis command line flag in nightly and local builds r=#dlp-reviewers!,haik!
Pushed by daparks@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7b683be273cc
Only consider -allow-content-analysis command line flag in nightly and local builds r=haik,dlp-reviewers,gstoll
Comment 4•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox134:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•