It says that it's "based on Chromium 81.0.4044.92" and the current desktop release is 83.0.4103.97. The first stable v83 release was May 19, 2020.
chromiumdash.appspot.com/releases?platf
81.0.4044.92 is from April 7th. There were 4 subsequent releases for v81 from April 15 through May 5.
Conversation
They also build with a GCC-based toolchain which loses important security features like type-based CFI. There are other problems with how they build it too. You are better off using a proper build of Chromium, although most Linux distributions lack the competency to provide that.
2
1
This Tweet was deleted by the Tweet author. Learn more
They think they know better, but they don't. By using GCC, they're losing type-based CFI and other security features. By using additional system libraries, they're weakening CFI and losing important changes. Inadvisable changes are often made due to lack of care / understanding.
2
2
The bulk of the changes being made by these forks are just changing defaults or removing optional features. There are few changes with real substance. Most of those are just changing where static assets are fetched, etc. There aren't any leaks of data for them to remove anyway.
1
2
how about ungoogled-chromium ? Keeps up to date and seems to have somewhat shared analogous goal in removing Google telemetry/dependencies from Chromium as GrapheneOS does in removing Google Play Services from Android
1
You're confused. The Android Open Source Project doesn't have Google apps and services. Google Play Services isn't part of baseline Android. It isn't part of AOSP and isn't part of what's officially required for an OS to be considered Android. It's not the purpose of GrapheneOS.
1
1
AOSP doesn't have any analytics/telemetry. Chromium analytics/telemetry is gated behind a toggle for submitting usage stats. The same goes for all the other Google services where data is submitted to them. Network connectivity checks and static asset downloads don't have toggles.
2
1
Not sure if I understood your sentence about network connectivity and e.g. DNS, but to add: They are preconfigured to google in AOSP (hardcoded). It can be changed via settings and overlays, however leaves a bad taste.
1
AOSP uses network-provided DNS by default, not Google DNS. It only has Google DNS as a fallback for nearly non-existent networks not providing DNS servers via DHCP. Not sure why that would leave a bad taste since it has to use something and the privacy policy isn't bad.
2
Anyway, that sentence was about Chromium, not AOSP. You're misunderstanding what I wrote and you need to pay attention to the context. AOSP doesn't download any assets from Google. Everything after the first sentence in twitter.com/DanielMicay/st was about Chromium, not AOSP.
Quote Tweet
Replying to @DanielMicay @nerdbusiness and @didymusw
AOSP doesn't have any analytics/telemetry. Chromium analytics/telemetry is gated behind a toggle for submitting usage stats. The same goes for all the other Google services where data is submitted to them. Network connectivity checks and static asset downloads don't have toggles.
Suggest reading grapheneos.org/faq#default-dns and the other sections about DNS since you're misunderstanding how it works.
1
Show replies