kchr

Thank you! Updated the post with a link to this resource.

You are absolutely right, I'll fix it asap!

DivestOS sounds interesting but I am wary of any "mission-critical" software project (such as the firmware for my primary phone) that relies on a single person, for multiple reasons. Burnout and potential for social engineering by malicious actors being two of them.

GP:s comment made me curious as well. Usually, if multiple hardware vendors are supported there are separate branches with different maintainers. It doesn't necessarily mean that the main codebase is bloated as a result.

For those that are looking to install GrapheneOS and want to ensure that their banking apps work as intended, here is a curated list of supported apps per country:

https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/

Rest assured, he won't get fooled again

– Ladies and gentlemen, we got'em.

For what it's worth, I chuckled at your comment. :-)

Rule #1: Never trust an Oracle license.

Security. The more popular a piece of software gets (including operating systems), it becomes a bigger attack surface for malicious actors to use.

Fundamentally, Windows security is not really that much of a swiss cheese people usually say it is. It's just that more people (researchers and malicious actors alike) are actively looking for vulnerabilities in it.

CPU vulnerability mitigations would typically be distributed with the intel-microcode package for Intel processors on Debian-based distributions, for example.