Closed
Bug 1329860
Opened 8 years ago
Closed 7 years ago
Ability to configure additional Safe Browsing providers through WebExtensions
Categories
(Firefox :: Distributions, defect, P2)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: hectorz, Assigned: mkaply)
References
(Blocks 1 open bug)
Details
(Whiteboard: [outreach, moz china add-on manager])
As a result of unstable internet access to Google, Beijing office operates https://sb.firefox.com.cn/lists?pver=2.2 with safe browsing data from Chinese providers, and works with Baidu to serve their data in compatible APIs, both for China repack users.
We need an API to register these additional service endpoints.
We currently also have an alternative design to credit all providers in about:blocked, and modified logic for a site owner to appeal to the data providers responsible for blocking their site.
We understand there's effort to improve multiple Safe Browsing provider support with the ongoing transition to Google Safe Browsing API v4.
Preferably these should be configurable with prefs, which we can tweak with distribution.ini, w/o exposing these through WebExtension API.
Comment 1•8 years ago
|
||
I think this should also be done as part of a bootstrap system addon rather than a webextension.
Component: WebExtensions: Untriaged → General
Product: Toolkit → Firefox
Updated•8 years ago
|
Assignee: nobody → mozilla
Component: General → Distributions
Assignee | ||
Comment 2•8 years ago
|
||
You can already set these values via distribution.ini, can't you?
Reporter | ||
Comment 3•8 years ago
|
||
(In reply to Mike Kaply [:mkaply] from comment #2)
> You can already set these values via distribution.ini, can't you?
For introducing new data providers only, I think yes, it's already possible.
(In reply to Hector Zhao [:hectorz] from comment #0)
>
> We currently also have an alternative design to credit all providers in
> about:blocked, and modified logic for a site owner to appeal to the data
> providers responsible for blocking their site.
>
> We understand there's effort to improve multiple Safe Browsing provider
> support with the ongoing transition to Google Safe Browsing API v4.
I've not checked the progress of these efforts to see if the credits/appealing parts are covered.
Updated•7 years ago
|
Whiteboard: [outreach, moz china add-on manager]
Comment 4•7 years ago
|
||
Mike is going to do the smooth hand-off to a team where this is being worked on (phishing) - timing need by Fx58
Flags: needinfo?(mozilla)
Updated•7 years ago
|
Priority: -- → P2
Comment 5•7 years ago
|
||
We marked this as a P2 for the part about giving credit to who is providing the blocking - since that is important for users to know and for the people providing blocking to get credit.
Updated•7 years ago
|
Assignee | ||
Comment 6•7 years ago
|
||
Clearing need info. I've commented in bug 1366384 which is where this work should be.
Flags: needinfo?(mozilla)
Assignee | ||
Comment 7•7 years ago
|
||
I'm marking this as WONTFIX.
WebExtensions won't support doing this. This will be done via a distribution file and the work for the credit will be in bug 1366384.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•