Safe Browsing toggle should be grayed out if we detect that the API key is invalid. |
||
Issue descriptionBy default, Chromium ships with an invalid Google API key, which means that Chromium builds cannot get database updates from Safe Browsing service. We should probably disable the Safe Browsing toggle in settings when we detect an invalid key to make sure that the user is correctly informed. See https://bugs.chromium.org/p/chromium/issues/detail?id=821989#c19.
,
Mar 21 2018
Also, the "Google API keys are missing. Some functionality of Chromium will be disabled." message is not clear enough that important security functionality (like Safe Browsing) will be disabled. Having the Safe Browsing toggle grayed out on its own is not enough - the user is not really expected to be constantly checking their settings to make sure that they are protected.
,
Apr 3 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by vakh@chromium.org
, Mar 16 2018Owner: vakh@chromium.org
Status: Assigned (was: Untriaged)