4 ms·
Interesting research. I have booted up Pixels using Qualcomm chips and have not seen the elusive izaticloud. The one issue with using GrapheneOS's connectivity
by joemazerino 4y ago
Interesting research. I have booted up Pixels using Qualcomm chips and have not seen the elusive izaticloud.
The one issue with using GrapheneOS's connectivity check is that you're broadcasting to the network that you're someone of interest. An Android phone connecting to Google isn't great for privacy but it is normal. An Android phone connecting to a GrapheneOS domain isn't.
- Tepix 4y agoPerhaps they only send this data once?
- flotzam 4y agoThat's why it's configurable in Settings > Network & internet > Internet connectivity check: GrapheneOS / Standard (Google) / Disabled
- joemazerino 4y agoYep, adding a toggle is a must-have.
- phh 4y ago> The one issue with using GrapheneOS's connectivity check is that you're broadcasting to the network that you're someone of interest. An Android phone connecting to Google isn't great for privacy but it is normal. An Android phone connecting to a GrapheneOS domain isn't. Thanks that's an interesting thought. I had similar thoughts, but going the other way around. I was wondering whether you gave more entropy be not using Google's generate_204, than by using it (= do more IPs do generate_204 calls). But after trying to compute some estimates, I ended up thinking that not sending generate_204 was still better than sending it. But yes, as you point out, the entropy provided by pinging /another/ generate_204 is much much higher. At this point, it depends if you want to lower the information you send to Google, or your carrier. PS: Just in case, Android's connectivity check pings a "generate_204" endpoints that as mentioned literally just responds with a 204
- matheusmoreira 4y agoGrapheneOS has settings to disable connectivity checks or use common Google servers in order to blend in.