New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 748182 link

Starred by 1 user
Status: WontFix
Owner:
vakh@chromium.org
Closed: Apr 2018
Cc:
█ bensanders@google.com
█ awoz@chromium.org
vakh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Make PVer4 work out-of-the-box for Chromium developers

Project Member Reported by vakh@chromium.org, Jul 24 2017 
As we roll out PVer4 to more users, Chrome developers will start to run into the situation where they are not using a personal GOOGLE_API_KEY so they get the default value of "dummytoken".

However, this key is not accepted by SafeBrowsing so the updates start to fail which means that these developers do not get SafeBrowsing protection at all.

Figure out and implement a solution to this.

Comment 1 by est...@chromium.org, Nov 10 2017

Labels: Hotlist-EnamelAndFriendsFixIt

Comment 2 by est...@chromium.org, Feb 18 2018

Labels: -Hotlist-EnamelAndFriendsFixIt

Comment 3 by vakh@chromium.org, Apr 3 2018

Status: WontFix (was: Assigned)
WontFix since this isn't a common usecase so not worth investing time in at the moment. Note that this does not apply to Chromium distributed by distros because they include the right GOOGLE_API_KEY.
►

Sign in to add a comment