Conversation

They do not share the goals or concepts of GrapheneOS at all. It is a bad target, they will always make bad targets for it, and they are not a viable partner or collaborator with an actual privacy/security focused project. Been burned already, others have too. No thanks.
2
1
You're bringing it up at the same time as Pine64 which has similar technical issues but without nonsense from the company / leadership including lots of harm. It's also a bad target, with no sign of ever wanting to make a good one, but at least they don't lie and cause harm.
1
1
At least Pine64 doesn't have deliberate anti-security measures and anti-security policies / ideology. It's just not technically advanced in that regard so it's far behind the status quo / industry standards (applies to both) but the reasons are better (lack of resources).
2
Anyway, if you want to support charlatans it doesn't just mean definitely not having my support, but I'll actively oppose it. Really not interested in building something offering trash tier security and robustness along with even worse usability. Not a long-term path either.
2
What you're talking about is already dead on arrival: remotely exploitable over the air via known vulnerabilities without being able to provide over-the-air patches for the issues. What's not terrible about rolling back security so much + not having updates?
2
If your laptop was purchased recently from a decent company, it will at least have firmware updates for all of the major components including Wi-Fi and Bluetooth, and you can apply those by keeping the OS up-to-date as long as it's decent. Of course, you did say *Debian* so...
2
distribution on a converted Samsung Chromebook or something similar, where you actually get a modern security architecture, etc. and just aren't using an OS on it with an application security model and modern mitigations but hardware underneath it is fully capable of all that.
1
Show replies