-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Traffic to Google observed when using Vanadium for the first time #118
Comments
Also seen:
The first POST sends about 13 apps in the JSON body plus some browser and OS info. |
This is documented in the FAQ and #62 is already open. |
They're not proprietary Google updates and it's not clear what you mean by that. GrapheneOS isn't yet hosting the static assets like dictionary updates, certification revocation lists, etc. and we'd need to figure out how to generate/build these separate or just obtain them from the official server in advance and host them ourselves. We'd need to host a component update server. Alternatively, it may be that we don't actually need to update any of this out-of-band. That hasn't been determined. You're welcome to work on it. It would be implemented already if people helped us out with these smaller tasks. |
I just didn't know what they were aside from binary blobs downloaded from Google. That's all. I'm no Chromium expert. But #62 has been made clear that the intention is to provide a GrapheneOS component update server so anything that's not about implementing that is off-topic, even if it's simply documenting unsolicited connections. I'd love to help with things but I've evaluated GrapheneOS for 2 days now and it sounds like the project wants people more familiar with long-term implementation goals. I'll refrain from logging more issues if I can't help with implementation. |
Unknown traffic was observed to update.googleapis.com and gvt1.com when running Vanadium for the first time.
Vanadium 93.0.4577.82
Is this downloading proprietary Google updates?
The below is a tshark/wireshark capture with a "dns or http" filter:
The text was updated successfully, but these errors were encountered: