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

Not calling home to google on about:blank, possible? #5

Open
JoachimHenze opened this issue Oct 20, 2023 · 5 comments
Open

Not calling home to google on about:blank, possible? #5

JoachimHenze opened this issue Oct 20, 2023 · 5 comments

Comments

@JoachimHenze
Copy link

JoachimHenze commented Oct 20, 2023

Thank you very much for creating that nice project! It is very valuable for users of Windows 2003, Windows XP, and also for the ReactOS project! I tried to boost the popularity of your project a bit by reactos/rapps-db#202

A request for the start:
Given that the user set up about:blank as default homepage.
If I do open the browser, I can see via netstat -abn that it seeks contact to some legitimate google servers.
What does the browser try to obtain from there? Can we turn that off? (the official Google Chromium sources M49.0.2623.112 does behave the very same!)

@jonm58
Copy link

jonm58 commented Oct 21, 2023

you mean Google safebrowsing?

@JoachimHenze
Copy link
Author

I am not sure what it is. I first want to understand what it is, and then have an option (or a hardcode) to disable it.
The definitionOfDone for this ticket is rather distinct: no initial network traffic when about:blank is set up as the start-page and the browser is just launched (the user has not interacted yet with the omnibox at this point).

@jonm58
Copy link

jonm58 commented Oct 21, 2023

Google Spy Browser
AD
www.google-analytics.com
2542116.fls.doubleclick.net
googleads.g.doubleclick.net
static.doubleclick.net
www.googletagmanager.com
maybe AD
safebrowsing.google.com
alt2-safebrowsing.google.com

No AD(Safe)
r3---sn-j5o7dn7z.gvt1.com、redirector.gvt1.com and google.com - Possibly downloading language packs、Dictionaries and updating extensions

"external_update_url": "https://clients2.google.com/service/update2/crx"

@JoachimHenze
Copy link
Author

Great, now let's get rid of that. :D

@JoachimHenze
Copy link
Author

@Alex313031 maybe you can have a look later at what win32ss did in the 3 commits that I linked here win32ss/supermium#402 (comment)
Maybe the same could be done for your Chromium-XP 49 later?

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

No branches or pull requests

2 participants