••••••••••••••••••••••••••••
The sad thing is that they are always way behind on security updates. Old kernels, old firmware, old drivers, all full of known high/critical CVEs. And then you are missing out on up to 1.5 years of fixes for non-major/critical vulnerabilities because they are still on Android 16 (only high/critical vulnerabilities are in ASBs). To make all of this worse, Google recently only started releasing fixes for some high/critical vulnerabilities on the latest Android version (currently Android 17). OEMs and Google somehow convinced people that having a recent ASB is enough, but it is only the tip of the iceberg. I have virtually no google besides what I want (maps) Well, except that /e/OS runs Google’s obfuscated DroidGuard binary in a privileged process to pass basic integrity. Yes, Google still has privileged access to your phone, unless you disable Play Integrity support in microG (which will break quite many apps). The even worse thing is that Google can send a unique DroidGuard blob just for you (since it is per request). Moreover, /e/OS gives certain Google apps more privileges than the standard Android app sandbox (Google Maps being one of them). Using it on a Fairphone eh? Well, you are also running proprietary Chinese TCL camera image processing blobs. —— People who care about privacy and security do not use /e/OS. It is LineageOS with Murena’s cloud crap on top, along with a pile of hacks that weaken security and privacy. Also, they are just very incompetent. E.g. Fairphone was hit by a bad bug where WiFi didn’t work on a lot of networks. When this was already known for months, Murena rolled out the same bug.
•••••••••••••••••••••••••••••••••••••••••
I didn't find the answer that interesting: Vint Cerf: In the early 1970s, while we were developing this, we asked ourselves, should there be patents associated with it? Should there be other constraints? Should it be a licensable thing? The government does license technology that it has paid to develop, but it can also release it openly. And we went through a kind of analysis. Remember that we were thinking this would be a substrate for the American command and control system that would use computers to support command and control. And that we knew that it would have to be interconnected to our allies. So then in 1973, '74, we're saying, well, who are our allies now in 1974? And there's this list. And then we said, well, who were our allies 25 years before that? And it was a different list. And we said, who will our allies be 25 years from now? And we didn't know. So we thought the only way we can be assured that the allies will have access to this is to simply open it up. So we published this openly. All the protocols were made available openly. We encouraged implementations and interoperability. Interoperability. Could I just say one thing about that word, interoperability? Literally, everything in my career has revolved around the ability of disparate and distributed systems to interwork with each other. And interoperability is its own reward. And so I think if there was any theme in my history and in my career, it's been the seeking interoperability among disparate systems
•••••••••••
 Top