Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New policies for safe browsing configuration #1028

Open
htcfreek opened this issue Jul 11, 2023 · 2 comments
Open

New policies for safe browsing configuration #1028

htcfreek opened this issue Jul 11, 2023 · 2 comments

Comments

@htcfreek
Copy link
Contributor

htcfreek commented Jul 11, 2023

As you have the policy DisableSecurityBypass/SafeBrowsing it would make sense to add a second set of policies to configure and lock the safe browsing settings.

Sure I can set all the preferences manually using the preferences policy, but this isn't the best way to go. We need multiple preferences for single check boxes and it is a bit confusing that after blocking safe browsing bypass rules the user can still disable the whole safe browsing feature.

The better and admin friendly way would be to have a dedicated set of policies. This helps finding the setting too.

And if you worry that admins disable the feature you could add a policy that only forces the enabled state.

List of preferences to set and lock:

  • Block dangerous and deceptive content sets:
    • browser.safebrowsing.malware.enabled
    • browser.safebrowsing.phishing.enabled
  • Warn me about unwanted and uncommon software sets:
    • browser.safebrowsing.downloads.remote.block_potentially_unwanted
    • browser.safebrowsing.downloads.remote.block_uncommon
  • Block dangerous downloads:
    • browser.safebrowsing.downloads.enabled
@mkaply
Copy link
Collaborator

mkaply commented Jul 11, 2023

The reason I've never done this is because these preferences are confusing and don't really map to the checkboxes well. (and every thing is enabled by default)

But I totally understand.

@htcfreek
Copy link
Contributor Author

Maybe it makes sense to at least add a hint in the description of DisableSecurityBypass/SafeBrowsing that it has nothing to do with the ui settings and that admins can use the prefs to manage the ui settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants