Closed
Bug 1579906
Opened 5 years ago
Closed 5 years ago
disable sending new TLS error reports
Categories
(Core :: Security: PSM, task, P1)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
mozilla71
People
(Reporter: keeler, Assigned: keeler)
Details
(Whiteboard: [psm-assigned])
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-esr68+
|
Details | Review |
We're re-thinking our TLS error reporting mechanism, and we need to disable sending new reports for now.
Assignee | ||
Comment 1•5 years ago
|
||
Pushed by dkeeler@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a80b7ebbd675 disable sending new TLS error reports while we rethink our approach r=kjacobs
Comment 3•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Assignee | ||
Comment 5•5 years ago
|
||
Comment on attachment 9093432 [details]
bug 1579906 - disable sending new TLS error reports while we rethink our approach r?kjacobs
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: Right now any TLS error reports that get sent are basically dropped by our servers, so this is just extra work clients are doing.
- User impact if declined: Extra unnecessary work.
- Fix Landed on Version: 71
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The patch flips a pref to disable a feature - it should be safe.
- String or UUID changes made by this patch: none
Flags: needinfo?(dkeeler)
Attachment #9093432 -
Flags: approval-mozilla-esr68?
Comment 6•5 years ago
|
||
Comment on attachment 9093432 [details]
bug 1579906 - disable sending new TLS error reports while we rethink our approach r?kjacobs
Disables a feature which isn't doing anything useful. Approved for 68.3esr.
Attachment #9093432 -
Flags: approval-mozilla-esr68? → approval-mozilla-esr68+
Comment 7•5 years ago
|
||
bugherder uplift |
status-firefox-esr68:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•