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

Disable variations service #1733

Open
pilgrim-brave opened this issue Oct 19, 2018 · 2 comments
Open

Disable variations service #1733

pilgrim-brave opened this issue Oct 19, 2018 · 2 comments

Comments

@pilgrim-brave
Copy link

@pilgrim-brave pilgrim-brave commented Oct 19, 2018

Service sends and receives information to Google servers periodically. According to https://cs.chromium.org/chromium/src/components/variations/service/variations_service.cc?l=232 it is only enabled for official Google Chrome builds, but there is also a command line switch to enable it.

At a minimum, we should ensure that the IFDEF for official Chrome builds is not being triggered, and also disable the command line switch.

As a defense-in-depth, we could also patch VariationsService::DoFetchFromURL https://cs.chromium.org/chromium/src/components/variations/service/variations_service.cc?l=506 to ensure it never issues a network request.

@pilgrim-brave pilgrim-brave added this to Release 1.0 in Network Audit Oct 19, 2018
@srirambv srirambv added this to the 1.x Backlog milestone Oct 19, 2018
@bbondy bbondy moved this from Release 1.0 to Untriaged Backlog in Network Audit Oct 30, 2018
@pilgrim-brave pilgrim-brave moved this from Untriaged Backlog to P3, P4, & P5 Backlog in Network Audit Oct 30, 2018
@rebron rebron modified the milestone: 1.x Backlog Feb 7, 2019
@tomlowenthal
Copy link
Member

@tomlowenthal tomlowenthal commented Aug 6, 2019

@jumde Could you check whether this is already fixed?

@jumde
Copy link
Contributor

@jumde jumde commented Aug 7, 2019

Not fixed yet, there are a couple of features using this service. Setting the estimate to 3 to make sure disabling this service does not cause any web-compat concerns.

@jumde jumde removed this from P3, P4, & P5 Backlog in Network Audit Oct 9, 2019
@rebron rebron added this to Untriaged Backlog in General Oct 9, 2019
@rebron rebron added the priority/P4 label Oct 15, 2019
@rebron rebron moved this from Untriaged Backlog to P4 Backlog in General Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
General
  
P4 Backlog
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.