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

Crash reporting connects to clientservices.googleapis.com on startup #3816

Closed
tildelowengrimm opened this issue Mar 20, 2019 · 12 comments · Fixed by brave/brave-core#2029 or brave/brave-core#2095
Assignees
Labels
priority/P1 A very extremely bad problem. We might push a hotfix for it. privacy/connect This requires making a network connection to a third-party service. QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Test-Plan-Specified QA/Yes release-notes/exclude

Comments

@tildelowengrimm
Copy link
Contributor

tildelowengrimm commented Mar 20, 2019

Crash reporting reaches out to clientservices.googleapis.com. Discovered when crash reporting was enabled by default in Nightly channel


Original issue description

Just installed Version 0.64.7 Chromium: 73.0.3683.75 (Official Build) nightly (64-bit).

Screen Shot 2019-03-20 at 14 33 11

@tildelowengrimm tildelowengrimm added the privacy/connect This requires making a network connection to a third-party service. label Mar 20, 2019
@bbondy
Copy link
Member

bbondy commented Mar 20, 2019

@tomlowenthal Do you know the full URL? I think we have a network audit in CI so not sure why it wouldn't catch it.
Only Nightly?

@tildelowengrimm
Copy link
Contributor Author

I think only Nightly, but I didn't reinstall Dev yesterday to check. It's not a behavior I've seen before, but I think the last time I tested was about a week ago with Dev. I don't have the URL because my firewall couldn't get that out of the HTTPS connection.

@jumde jumde self-assigned this Mar 21, 2019
@pilgrim-brave
Copy link

Potential sources:

  • components/metrics/url_constants.cc::kNewMetricsServerUrl
  • components/variations/variations_url_constants.cc::kDefaultServerUrl

@pilgrim-brave
Copy link

OK according to PJ it's kNewMetricsServerUrl

@simonhong
Copy link
Member

simonhong commented Mar 22, 2019

I think this happened by brave/brave-core#1985.
That PR turned on metrics reporting by default for dev/nightly for crash reporting.
That means latest dev have same issue if user don't it off explicitly.
So, stable/beta could have this issue when user turn on crash reporting explicitly.

@rebron rebron added the priority/P1 A very extremely bad problem. We might push a hotfix for it. label Mar 22, 2019
@jumde jumde modified the milestones: 0.64.x - Nightly, 0.62.x - Beta Mar 26, 2019
@jumde jumde removed this from the 0.62.x - Beta milestone Mar 27, 2019
@jumde
Copy link
Contributor

jumde commented Mar 28, 2019

Re-opened with C74 revert

@srirambv
Copy link
Contributor

srirambv commented Apr 1, 2019

@jumde any test plan for the CI builds? I only see npm tests on #2095 .

@kjozwiak
Copy link
Member

kjozwiak commented Apr 1, 2019

Assuming @LaurenWags and myself can check using Little Snitch to make sure we're not connecting to clientservices.googleapis.com at startup. As @srirambv mentioned above, is there a better way to Win/Linux?

@jumde
Copy link
Contributor

jumde commented Apr 1, 2019

@kjozwiak @srirambv - Fiddler works really well on Win/Linux https://www.telerik.com/download/fiddler

@btlechowski @srirambv - Test plan specified here: brave/brave-core#2095

Let me know if you have any questions.

@bsclifton bsclifton changed the title Brave nightly connects to clientservices.googleapis.com on startup Crash reporting connects to clientservices.googleapis.com on startup Apr 1, 2019
@btlechowski
Copy link

btlechowski commented Apr 1, 2019

Edit: Below findings are a know issue: #1947

On Windows 10 x64, Brave connects to gvt1.com domain.

Steps:

  1. Clean profile
  2. Go to settings through hamburger menu

URLs:

http://redirector.gvt1.com:443
https://redirector.gvt1.com/edgedl/chrome/dict/en-us-8-0.bdic
http://r5---sn-f5f7lnel.gvt1.com:443
https://r5---sn-f5f7lnel.gvt1.com/edgedl/chrome/dict/en-us-8-0.bdic?cms_redirect=yes&mip=188.121.0.11&mm=28&mn=sn-f5f7lnel&ms=nvh&mt=1554156499&mv=m&pl=19&shardbypass=yes

Tested on

Brave 0.62.49 Chromium: 73.0.3683.86 (Official Build) (64-bit)
Revision f9b0bec6063ea50ce2b71f5b9abbae7beee319a6-refs/branch-heads/3683@{#858}
OS Windows 10 OS Build 17134.523

@btlechowski
Copy link

btlechowski commented Apr 1, 2019

Verification passed on

Brave 0.62.49 Chromium: 73.0.3683.86 (Official Build) (64-bit)
Revision f9b0bec6063ea50ce2b71f5b9abbae7beee319a6-refs/branch-heads/3683@{#858}
OS Windows 10 OS Build 17134.523
Brave 0.63.28 Chromium: 73.0.3683.75 (Official Build) beta (64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Windows 10 OS Build 17134.523

Used test plan from brave/brave-core#2095
Reproduced #1947 while testing

Verification PASSED on macOS 10.14.3 x64 using the following build:

Brave 0.62.49 Chromium: 73.0.3683.86 (Official Build) (64-bit)
Revision f9b0bec6063ea50ce2b71f5b9abbae7beee319a6-refs/branch-heads/3683@{#858}
OS Mac OS X

Screen Shot 2019-04-01 at 8 14 10 PM

  • ensured that Brave doesn't contact any Google API's at startup
  • ensured that Brave doesn't contact any Google API's after enabling crash reports
  • crashed via brave://crash and ensured that Brave didn't contact Google API's after sending report
  • crashed via chrome://gpu and checked the same case as mentioned above
  • left Brave running for ~1hr or so and ensured we didn't contact any Google API's

Verified passed on macOS 10.13.6 with

Brave 0.62.49 Chromium: 73.0.3683.86 (Official Build) (64-bit)
Revision f9b0bec6063ea50ce2b71f5b9abbae7beee319a6-refs/branch-heads/3683@{#858}
OS Mac OS X
  • Verified test plan from Issue 3816: Disabling metrics services provider brave-core#2095
  • Verified that Brave doesn't contact any Google API's at startup
  • Verified that Brave doesn't contact any Google API's after enabling crash reports
  • Crashed via brave://crash and verified that Brave didn't contact Google API's after sending report

Screen Shot 2019-04-01 at 7 16 21 PM

Verification passed on

Brave 0.63.29 Chromium: 73.0.3683.75 (Official Build) beta (64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Linux

Screenshot from 2019-04-02 16-09-09

@kjozwiak
Copy link
Member

kjozwiak commented Apr 2, 2019

@LaurenWags if the above worked for you, can you label this as QA/Passed for macOS? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment