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

Proxy sb-ssl.google.com through sb-ssl.brave.com #4328

Closed
jumde opened this issue May 6, 2019 · 3 comments · Fixed by brave/brave-core#2377
Closed

Proxy sb-ssl.google.com through sb-ssl.brave.com #4328

jumde opened this issue May 6, 2019 · 3 comments · Fixed by brave/brave-core#2377
Assignees
Labels
priority/P2 A bad problem. We might uplift this to the next planned release. privacy/connect This requires making a network connection to a third-party service. privacy QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Test-Plan-Specified QA/Yes release-notes/include security

Comments

@jumde
Copy link
Contributor

jumde commented May 6, 2019

Test Plan specified here: brave/brave-core#2377

@jumde jumde self-assigned this May 6, 2019
@jumde jumde added the privacy label May 6, 2019
@diracdeltas diracdeltas added privacy/connect This requires making a network connection to a third-party service. priority/P2 A bad problem. We might uplift this to the next planned release. labels May 6, 2019
@gadfsgagfaq435
Copy link

(sorry if this is the wrong place to ask just delete the comment)

i just saw this by pure chance and was shocked and instantly disabled safebrowsing in brave
my question: if this is fixed will safebrowsing be completely "contact-free" from google in brave ?
so will my ip-adress and/or the websites i visit ever reach google if i use safe-browsing in brave ?
(i know right now it definitly does once i download an .exe according to this "bug" but i mean once this issue is fixed)

thanks.

@diracdeltas
Copy link
Member

diracdeltas commented May 7, 2019

@gadfsgagfaq435 Google Safebrowsing for URLs doesn't send the website to Google, only a hash prefix if there is a potential match: https://developers.google.com/safe-browsing/v4/urls-hashing. In most cases it won't need to send anything.

For downloads, it appears to send more info (which we weren't aware of til now): https://cs.chromium.org/chromium/src/components/safe_browsing/proto/csd.proto?sq=package:chromium&dr=CSs&g=0&l=443-718 [EDIT: these protos may be out of date, we're figuring it out now)

We are going to make sure all these requests are proxied so Google at least does not get IP. For downloads, we are going to at least disable SB in Tor mode and maybe also in normal mode, not sure yet.

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented May 13, 2019

Verification passed on

Brave 0.64.75 Chromium: 74.0.3729.131 (Official Build) (64-bit)
Revision 518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS Windows 10 OS Build 17134.523

image

Verification passed on

Brave 0.64.75 Chromium: 74.0.3729.131 (Official Build) (64-bit)
Revision 518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS Linux
  • Verified no request sent to sb-ssl.google.com when visiting testsafebrowsing.appspot.com
    Screenshot from 2019-05-13 11-06-55

Verification PASSED on macOS 10.14.4 x64 using the following build:

Brave 0.64.75 Chromium: 74.0.3729.131 (Official Build) (64-bit)
Revision 518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS Mac OS X

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/P2 A bad problem. We might uplift this to the next planned release. privacy/connect This requires making a network connection to a third-party service. privacy QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Test-Plan-Specified QA/Yes release-notes/include security
Projects
None yet
7 participants