• 20 Posts
  • 233 Comments
Joined 2 years ago
cake
Cake day: March 19th, 2024

help-circle
  • The new repo has two releases in it now. These releases are not signed with the original key as far as I can tell. Further, GitHub is silently redirecting to the new repo, even in Obtainium, meaning it’s possible that if you had this previously installed via Obtainium and updated now, you may have unsigned apks installed that may or may not contain the changes in the repo.

    This is a mess. I deleted the repo from Obtainium (luckily I don’t auto install updates) and will wait to see what happens over the next few months. Might just save my notes in a network share instead of using syncthing from my phone. Idk, notes are all that I was using it for.



  • Well, yes, but that is not exclusive to Pixels, and in fact, most phones (other than the latest iPhones) are more vulnerable. Pixels, especially the latest devices, have the best hardware security features of any Android phone (unfortunately). You’re focused on Pixel, but that’s only because of the recent leaks which specifically focused on Pixel because of their breaching difficulty. Here’s the full matrix from last year (which hasn’t leaked as recently):

    https://discuss.grapheneos.org/d/14344-cellebrite-premium-july-2024-documentation

    GrapheneOS, even now, is not vulnerable for several reasons, most of which tie into the hardware features of the Pixel. There’s a reason Graphene only works on Pixel.

    All I’m saying is that it’s entirely misleading to imply that only Pixels are vulnerable. This is not the case, even for iPhones.

    I’m also not sure why you seem to be trying to say I disagree on the fact that Google is happy to leave vulnerabilities wide open, when that is exactly what I said in my original comment. Their new release schedule allows them to leave these vulnerabilities open for an even longer time, making Cellebrite’s job easier.













  • You keep saying this, but then do not elaborate very much. A lot of your comments in this thread have been something about Bazzite being bad/complicated/slow. Bazzite is not necessarily more complicated, it’s actually a lot less complicated in most ways and is difficult to break by design, as are other immutable distros. This is precisely why it is pushed to new Linux users. It’s a good starting point to have something that just works and not have to worry about much. I think a lot of long time Linux users are used to having full control over every piece of the OS, and have (like yourself) come to expect all distros to work that way. That’s fine and I totally understand that, but you should also consider that those who have not built the same habits from non-immutable might prefer a more hands off approach. I’ve used Linux for almost two decades, and I daily drive immutable because it’s so stable. I’m able to scratch the itch of wanting to mess with stuff by using distrobox, and if I’m really messing around, just using rpm-ostree. Sure, it’s different than normal distros, and it’s not for everyone, but it got my partner to use Linux on their own without any issues.

    It’s okay to suggest other options for sure, but don’t get snarky when people are suggesting what works for them. The main benefit of Linux is that you have a choice in the first place, and you aren’t going to be stuck with whatever distro you’re using if they decide to do something catastrophic.

    There is no such thing as a one-fits-all distro.