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

Issue 15: Set the fallback URL for google extensions/components to componentupdater.brave.com. #16

Merged
merged 1 commit into from
Feb 12, 2019

Conversation

jumde
Copy link
Contributor

@jumde jumde commented Feb 5, 2019

Fix #15

Description

CRLSets which is maintained by google will be enabled by default in Brave to handle revoked certificates on all platforms. To prevent any connections to google servers by default we are setting the fallback URL for google extensions and components to componentupdater.brave.com which removes any user identifiable information before forwarding the requests to the google component update server.

More details here: brave/brave-browser#518

auditors: @bbondy, @bsclifton, @diracdeltas

CRLSets PR: brave/brave-core#1581

Feel free to DM if you need more info.

Test Plan

  • Before CRLSets

    • MacOS:

      • Default extensions installed at start
      • No connections by default to Google servers
      • Brave component updates work
      • Individual component updates work
      • No component status errors on restart
      • Errors when go-updater is stopped
      • New extensions installed correctly
      • Updating extensions works correctly
    • Linux:

      • Default extensions installed at start
      • No connections by default to Google servers
      • Brave component updates work
      • Individual component updates work
      • No component status errors on restart
      • Errors when go-updater is stopped
      • New extensions installed correctly
      • Updating extensions works correctly
    • Windows:

      • Default extensions installed at start
      • No connections by default to Google servers
      • Brave component updates work
      • Individual component updates work
      • No component status errors on restart
      • Errors when go-updater is stopped
      • New extensions installed correctly
      • Updating extensions works correctly
  • After CRLSets

    • MacOS:

      • Default extensions installed at start
      • No connections by default to Google servers
      • Brave component updates work
      • Individual component updates work
      • No component status errors on restart
      • Errors when go-updater is stopped
      • New extensions installed correctly
      • Updating extensions works correctly
    • Linux:

      • Default extensions installed at start
      • No connections by default to Google servers
      • Brave component updates work
      • Individual component updates work
      • No component status errors on restart
      • Errors when go-updater is stopped
      • New extensions installed correctly
      • Updating extensions works correctly
    • Windows:

      • Default extensions installed at start
      • No connections by default to Google servers
      • Brave component updates work
      • Individual component updates work
      • No component status errors on restart
      • Errors when go-updater is stopped
      • New extensions installed correctly
      • Updating extensions works correctly

componentupdater.brave.com.

CRLSets which is maintained by google will be enabled by default in Brave to
handle revoked certificates. To prevent any connections to google servers by
default we are setting the fallback URL for google extensions and components to
componentupdater.brave.com which removes any user identifiable information
before forwarding the requests to the google component update server.

More details here: brave/brave-browser#518

auditors: @bbondy, @bsclifton, @diracdeltas
@jumde jumde merged commit ea90dc6 into master Feb 12, 2019
@bsclifton bsclifton deleted the update_default_url branch February 13, 2019 19:11
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

Successfully merging this pull request may close these issues.

2 participants