brave/brave-browser

Add group policy to configure shields default filterlists rather than URL specifics only

Open

#41,429 opened on Oct 6, 2024

View on GitHub
 (2 comments) (1 reaction) (1 assignee)JavaScript (2,164 forks)batch import
enterprisefeature-requestfeature/shieldsgood first issuehelp wanted

Repository metrics

Stars
 (16,194 stars)
PR merge metrics
 (Avg merge 4h 38m) (19 merged PRs in 30d)

Description

Platforms

Linux, macOS, Windows

Description

In https://github.com/brave/brave-core/pull/25710 we started to migrate towards group policies that match how Chromium does it. We currently have a few group policies for Brave specific features and this issue is to add a new policy that would allow a group policy admin to configure default filterlists themselves in shields as well. This may be useful for them to produce their own internal filterlist rule sets and turn them on by default or to configure a different default set of the predefined rules for administrative reasons.

Contributor guide

Research direction
Examine the existing Chromium group policy infrastructure and Brave's shield filterlist configuration to implement a new policy that allows admins to set default filterlists. Refer to PR #25710 for migration approach.
Tech stack
cppjavascript
Domain
desktopsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitC++Chromium policies
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50