commit abb1a8cf2ce822645d135677bcd77df2160d0de7
author Kelvin Jiang <kelvinjiang@chromium.org> Mon Oct 02 20:05:54 2023
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Mon Oct 02 20:05:54 2023
tree 31708120f117a2f648666c796f094fb68c4f1e28
parent c177ac9b5cc6705632cbf88f14680a4902b8080e

[DNR] Add "unsafe" rule count to RulesetMatcher

"safe"/"unsafe" rules are only applicable for dynamic and session
scoped rulesets.
 - a DNR rule considered "safe" if it poses less of a security concern
   and is less likely to leak or access data (not necessarily because
   it is totally safe). By this definition, block, allow, upgradeScheme
   and allowAllRequest rules are "safe".
 - all other DNR rules (by action) are considered "unsafe".

This CL computes this "unsafe" rule count by iterating over the list of
extension url rule metadata when the matcher is created.

For dynamic and session RulesetMatchers, whenever the ruleset is
updated, the RulesetMatcher is re-created and the unsafe rule count
will be recalculated.

Bug: 1485747
Change-Id: If054e65690df2ce91f2ca227c4b860876c253084
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4887636
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Commit-Queue: Kelvin Jiang <kelvinjiang@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1204230}