-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 gaia in brave-core #527
Comments
could you list which domains are from gaia? i'm seeing some which might not be |
On v 0.53.0. Here is the list of domains that I see on connect:
Here is a set of domains from gaia: Issue to prevent connection to other google domains is tracked here - #663 |
can this issue be fixed by setting the gaia URL constants to |
That might be a good solution, there may be side effects though. I can take a shot at this. |
No connections are made to the gaia domains on |
fyi, on 0.55.2 i see (after installing, on first startup, without any browsing):
|
New change landing in Gaia URL will effectively always go to |
Using
This is what I see with LittleSnitch (first run, no browsing, using steps found here: #514 (comment)) |
@LaurenWags i think those are all for extension updates (PDFJS), not Gaia related. |
Per discussion in slack, we're planning to serve PDFJS from the go-updater server rather than letting the browser connect to Google. |
Moved this PDFJS sitch to its own issue: #1669 (nice). |
Sorry if not posting in the right issue, but i saw this old one still open so I thought it would be good to share my findings from 2020. Brave still opens connections even with addons disabled and safebrowsing disabled, as follows: upon startup: seen rarely at random times: |
cc: @jumde on above comments (RE: specific domains) We should be blocking GAIA, unless you have the Should this be closed? |
This is controlled by the flag |
On startup, Brave gets a list of the google accounts from gaia, which connects to accounts.google.com. Disable gaia to avoid these connections.
The text was updated successfully, but these errors were encountered: