1354115 - remove special WebSense rules for non-blacklisted and unknown WebSense users.

Status: RESOLVED FIXED

(Release Engineering :: Release Requests, enhancement, P1)

Description

[[e-mail] (:bhearsum)]

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.

Because the relevant Balrog rules are shared across the test and live channels, I think we should remove them around the time that we ship to -cdntest (otherwise we potentially invalidate some of QE's update testing). We also need to update the release promotion configs to remove all of the new alias' for bypass rules and such. This can be done at any time.

Comment 1

[[e-mail] (:bhearsum)]

Attachment: remove websense bypass rules from automation configs

This is simply a backout of the two patches from https://bugzilla.mozilla.org/show_bug.cgi?id=1348922.

Comment 2

[Johan Lorenzo [:jlorenzo]]

Comment on attachment 8855293 [details] [diff] [review]
remove websense bypass rules from automation configs

Looks good to me!

Comment 3

[[e-mail] (:bhearsum)]

Just before we go to cdntest for 53.0, it looks like we need to remove the following rules:
* 449 (uses the original, version-less WebSense detection, which very few people have, and is essentially the equivalent of unknown websense)
* 545, 559, 555 (bypass rules for '(nowebsense)')
* 531, 560, 556 (bypass rules for non-blacklisted websense)
* 546 (the rule that holds unknown websense status on their current version)

We also need to s/'(nowebsense)'/Windows_NT/ on rule id 450, to have it catch all Windows users instead of just known-not-websense users.

Rail, does that look right to you?

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/73dd5487deea
remove special WebSense rules for non-blacklisted and unknown WebSense users. r=jlorenzo

Comment 5

[[e-mail] (:bhearsum)]

Comment on attachment 8855293 [details] [diff] [review]
remove websense bypass rules from automation configs

https://hg.mozilla.org/integration/mozilla-inbound/rev/73dd5487deead3ff6b3053c428dd8e0d6996d81b
https://hg.mozilla.org/releases/mozilla-aurora/rev/e03c56f3a839d1575e87dbd782638ad4894429e8
https://hg.mozilla.org/releases/mozilla-beta/rev/390df62a9c2ee8f4fc4b168a81e61bf23a435a0c
https://hg.mozilla.org/releases/mozilla-release/rev/bc7c1417bca4abe1e7ebeaeb4d11d16b4b4c252b

Comment 6

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

https://hg.mozilla.org/mozilla-central/rev/73dd5487deea

Comment 7

[Rail Aliiev [:rail]]

(In reply to Ben Hearsum (:bhearsum) from comment #3)
> Just before we go to cdntest for 53.0, it looks like we need to remove the
> following rules:
> * 449 (uses the original, version-less WebSense detection, which very few
> people have, and is essentially the equivalent of unknown websense)
> * 545, 559, 555 (bypass rules for '(nowebsense)')
> * 531, 560, 556 (bypass rules for non-blacklisted websense)
> * 546 (the rule that holds unknown websense status on their current version)
> 
> We also need to s/'(nowebsense)'/Windows_NT/ on rule id 450, to have it
> catch all Windows users instead of just known-not-websense users.
> 
> Rail, does that look right to you?

Sounds correct to me.

Comment 8

[Johan Lorenzo [:jlorenzo]]

Just to keep track on this dashboard: https://bugzilla.mozilla.org/buglist.cgi?resolution=---&status_whiteboard=%5Breleaseduty%5D&list_id=13535814&status_whiteboard_type=allwordssubstr&query_format=advanced

Comment 9

[[e-mail] (:bhearsum)]

(In reply to Ben Hearsum (:bhearsum) from comment #3)
> Just before we go to cdntest for 53.0, it looks like we need to remove the
> following rules:
> * 449 (uses the original, version-less WebSense detection, which very few
> people have, and is essentially the equivalent of unknown websense)
> * 545, 559, 555 (bypass rules for '(nowebsense)')
> * 531, 560, 556 (bypass rules for non-blacklisted websense)
> * 546 (the rule that holds unknown websense status on their current version)
> 
> We also need to s/'(nowebsense)'/Windows_NT/ on rule id 450, to have it
> catch all Windows users instead of just known-not-websense users.
> 
> Rail, does that look right to you?

Liz and I did most of this on Wednesday, and I finished it up today.