Closed
Bug 1351463
Opened 8 years ago
Closed 8 years ago
Bypass websense rule for manual update checks for 47.0.2-51.x that have no indication of websense
Categories
(Release Engineering :: Release Requests, enhancement, P2)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: ddurst, Unassigned)
Details
Because system add-ons don't update unless the client has elected for automatic updates, users that have chosen manual update checks could be needlessly held back due to no-indication (where "no-indication" means: neither '(websense-' nor '(nowebsense)' is in the update URL).
Because 47.0.2 is a watershed (due to SSE2) and this is solved in 52 -- and everything in between has a complicated tangle of hotfix, system addon, and build + system addon -- for 47.0.2 - 51.x (inclusive), if there is no indication of websense in the update URL and force=1 is present, we should bypass any websense-related prevention in balrog and let the user update.
The percentage of the no-indication audience for whom websense == true and manual update == true should be small enough to outweigh the benefit of propelling forward the complement (those who are set to manual update == true and websense == false).
Comment 1•8 years ago
|
||
"force" can't be used to make decisions like this in Balrog. It only affects whether we roll a die to determine if a request gets an update at all.
We can kindof sortof make this happen by letting *anyone* who makes a manual update request and has unknown websense status update to latest. That has the possibility of letting users on bad WebSense versions through as well. Maybe that's a risk we should accept.
Component: Balrog: Frontend → Releases
QA Contact: bhearsum → rail
Updated•8 years ago
|
Priority: -- → P2
Comment 2•8 years ago
|
||
In a recent e-mail thread we (releng, relman, and others involved with WebSense discussions) decided that when we ship 53.0, we will no longer hold back updates for non-blacklisted WebSense users nor users whose WebSense status is unknown. This will be fixed as part of that, which is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1354115
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•