this post was submitted on 23 Mar 2024
95 points (93.6% liked)

Privacy

32165 readers
145 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

*In terms of privacy, customisation, camera quality, and battery time.

For the longest time I have only used either iPhone or Samsung. I plan on switching to Android for the next phone I get, but I find that Samsung phones are often too big for me and put too much energy on camera quality (I don’t take many photos). I have started to look into brands such as Nokia and Motorola, and I would like to know what you guys think of them. Additionally, do you suggest any other phone brands aside from them? My biggest priorities are privacy and long battery time. Bonus if the phone can run LineageOS (I have excluded Graphene as they are only compatible with Pixel phones).

Thank you for any answers. Cheers!

you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 1 points 8 months ago (1 children)

seems to get pressured by Daniel Micay (thestinger) himself and his minion/mod mbananasynergy in GitHub issues all the time

I read a few of those, and I didn't see any kind of pressure, just clarifications. And they provided information on not just GrapheneOS, but LineageOS and AOSP.

That's exactly how I would handle things as well if I was working on a project and someone publishes a comparison table that gets posted a few places.

As for why GrapheneOS is mostly green, I guess there are three explanations:

  • GrapheneOS is really that good
  • GrapheneOS happens to meet all the metrics the author is interested in
  • nobody has bothered adding other fields (most likely)

But it's also not all green, GrapheneOS gets red for Google Pay compatibility and device support, which are two pretty important categories for many people.

If you know of categories where GrapheneOS doesn't do well, by all means, suggest them in an issue or open a PR. It's the best comparison I've seen, and seems worthwhile to contribute to.

It is either impossible for one person

Well yeah, Linus Torvalds does almost no actual development, but he's involved in merging patches. That job has value, and the end result is that people trust his branch.

That's the same way I see GrapheneOS or any Linux distro, it's just a handful of patches and configurations on top of a common core. AOSP is a high quality OS and there are lots of independent researchers looking at it, so it's a good base to build on, with the main problem being integration with Google services. Forking it is a huge task, so they should stay as close to AOSP as they can while achieving their goals.

And yeah, if GrapheneOS is an embargo partner, that's has a lot of value, and I hope other ROMs are able to get that as well. Faster access to patches is a good thing.

Code can be bought. Developers can be bought

Sure, and that would likely be pretty obvious, and can happen to pretty much any project. But the community could easily fork it and move on if that happens. That's what GrapheneOS did when they split from CopperheadOS, and that's what'll happen if GrapheneOS is bought or compromised.

So the real concern isn't with copyright, but with Trojan Horse inclusions, which is where security researchers come in. GrapheneOS has documented how to audit their changes vs AOSP, and they share code with other projects, which apparently has uncovered more bugs. That sounds pretty responsible to me.

Micay wants to steer everyone away from Firefox towards Chrome

But Chrome is superior to Firefox on mobile in terms of security because Mozilla hasn't ported many of the security features from the desktop browser. That's a fact. There's also an argument that Chrome is more secure on desktop as well, but there are tradeoffs to that.

I don't see any evidence that Micay prefers closed source code (most of Chrome is open source btw), so I'm not sure where this is coming from.

Fuchsia is the future, where Google's microkernel

Well yeah, Fuchsia is incredibly interesting and mikrokernels have fantastic security and isolation properties. If Google can pull it off, it'll be a really interesting kernel to use.

However, there's a reason mikrokernels aren't very popular: they're kind of difficult to work with. It just so happens that having your drivers in kernel space is incredibly convenient and performant. RedoxOS is another interesting mikrokernels project, and both Windows and macOS' kernels are moving that direction (both are hybrid kernels).

So it's only natural for him to be excited by it, I'm excited too. I don't like Google much, but their FOSS R&D side is really interesting. I don't know if he's a "fanboy" (I haven't bothered to do more than a cursory read of the links you've provided), but that's only relevant if it impacts his security choices (e.g. trusts Google with user data "for security").

feature rebranding plus firewalls, app permission modifications and stuff you can do without rooting, I see absolutely no reason how it claims to be better than anything else

Sane defaults has a ton of value. Most people don't know how to configure an OS to be secure.

It's not the only option obviously, that's just stupid dogmatism, but it is a good option, and perhaps the best option out of the box. There are also security features that Pixels have that other phones either don't or lock away from users, so GrapheneOS can have even better defaults than others due to the hardware it's limited to (e.g. the open bootloader). Whether that matters to you depends on what you're looking for.

So I'll agree that dogmatism should be policed, but ideally with reminders and not comment removals. Maybe have a three strikes policy or something if you're worried about repeat, intentional offenders.

why Google hardware is backdoored by NSA

I'm guessing most phones are, or at least compromised by the NSA. The NSA's job is to maintain backdoors to go after national security threats, so there's no reason to expect any default configuration to protect you.

Projects like GrapheneOS try to protect you as much as they can, but at the end of the day, anything that touches a network is going to risk.

That's why I'm so excited about Linux phones, the Pinephone and Librem 5 both have hardware kill switches for times when you're worried about surveillance.

Snowden lives in Russia to stay alive

Yet Snowing allegedly recommends GrapheneOS. Unless you think Micay is bullying Snowdon as well...

That said, I don't put a ton of stock into what Snowdon has to say. He's not a security expert, he's just a contractor who got away with government documents. He's careful, but fairly average.

Apple's security chips have all been pwned, and their latest one also got pwned recently

Sure, that's going to happen because they're a big target. That said, it's unlikely to impact regular users because those attacks are quite sophisticated and often caught by security researchers pretty quickly. The Android market is more sketchy because there's so much more diversity to the point where security researchers are going to miss a lot.

Regardless, staying up to date on security patches is the best line of defense, and sandboxing everything is the next line. GrapheneOS provides both.

"security by obscurity"

Ok, you lost me here. What they're providing is security by layers (sandboxing, reducing attack surface by having less stuff running, etc) and rapid security updates from upstream.

The proper solution is to completely open source the telephony stack, but that's not happening for any phone (though the Pinephone community is reverse-engineering theirs, so that's cool).

[–] TheAnonymouseJoker@lemmy.ml 1 points 8 months ago* (last edited 8 months ago) (1 children)

As for why GrapheneOS is mostly green, I guess there are three explanations: GrapheneOS is really that good

No, it clearly is not. If it provides nothing over AOSP forks, there is no reason why it is better. Maybe you did not read the propaganda dissemination they do, which I sent as a screenshot of their Telegram chats.

Here, I provide it again. https://imgur.com/a/fpcsIL2

If you know of categories where GrapheneOS doesn't do well,

If feature rebranding does anything other than cosmetic or placebo changes, do tell me. Anyone can do it. It improves nothing functionally. Modifying app permissions and using a strong firewall can be done without root and is far more risk free and incomparably easier than flashing a custom Android fork. There is nothing "out of the box" about flashing a custom ROM on any phone for most people in the world, including tech users.

Well yeah, Linus Torvalds does almost no actual development, but he's involved in merging patches. That job has value, and the end result is that people trust his branch.

He also happened to create the Linux kernel by himself and developed it himself for a very long time, until it started getting more contributors. He did all the development needed to be done.

yeah, if GrapheneOS is an embargo partner, that's has a lot of value, and I hope other ROMs are able to get that as well. Faster access to patches is a good thing.

That is very shady. A Google partnership is avoided by other custom build makers like LineageOS for a reason. That is enough reason to stay away from Graphene.

But Chrome is superior to Firefox on mobile in terms of security because Mozilla hasn't ported many of the security features from the desktop browser. That's a fact.

Who decided this fact? Micay's propaganda? Because Tor Project avoids Chromium base for both desktop and mobile browsers for multiple reasons, one of them being security. Chromium is incredibly leaky, insecure and anti-anonymity.

https://trac.torproject.org/projects/tor/wiki/doc/ImportantGoogleChromeBugs

You think Micay and his GPT tier filler has even 1% credibility compared to TailsOS professionals who maintain supremacy over state actors?

Sane defaults has a ton of value. Most people don't know how to configure an OS to be secure. It's not the only option obviously, that's just stupid dogmatism, but it is a good option, and perhaps the best option out of the box

There is nothing OOTB about flashing a custom Android build on a specific phone brand/model people buy with a lot of money. It risks bricking, alongside the obvious thing about Graphene community being insanely vitriolic as far as tech support questions go. Non root hardening is risk free, easy, achieves same goals and is a transparent process.

I'm guessing most phones are, or at least compromised by the NSA. The NSA's job is to maintain backdoors to go after national security threats, so there's no reason to expect any default configuration to protect you.

Huawei was sanctioned by USA partly because they refused to put NSA backdoors in it, and western agencies failed to find any Chinese backdooring in it, since they were provided source code to analyse. The ban eventually happened due to market protectionist reasons similar to what is happening to Tiktok now, or Alstom, Toshiba, IPTN and others.

Yet [Snowing allegedly recommends GrapheneOS]

That said, I don't put a ton of stock into what Snowdon has to say. He's not a security expert, he's just a contractor who got away with government documents. He's careful, but fairly average.

Snowden is not a security expert, but an OPSEC expert. Wildly different things. He was a spy. He was able to practice his OPSEC without fail and modify it on the go. His advice is not meaningful, and this tweet is irrelevant because too many things happened since 2019. He acts more like the "Symbol of Peace" like All Might in Boku no Hero Academia anime show, like some sort of symbolic "hero" figure.

Few years ago, in 2021, without any community consensus, Micay added a shutter sound for camera which could not be muted, putting the target audience of this tool/product at risk of jail or even death – privacy users, journalists and activists. https://old.reddit.com/r/privacytoolsIO/comments/pjl4bh/what_is_your_opinion_of_grapheneos_conforming_to/ So, how is Snowden's 2019 tweet relevant? How can anyone seriously trust Graphene one bit?

That said, it's unlikely to impact regular users because those attacks are quite sophisticated and often caught by security researchers pretty quickly. The Android market is more sketchy because there's so much more diversity to the point where security researchers are going to miss a lot.

It was established by Zerodium few years ago that Android's zero days cost more than iOS' zero days, and that Android's open source security model has surpassed whatever obscure security Apple has. That gap has continued to widen.

If there is a permanent hardware vulnerability, it will impact security just like Spectre, Meltdown and others affect Intel chips. Apple's phones and devices with "security enclave" chips are all permanently vulnerable. Androids as a whole are far more secure, and it is Apple that is sketchy, not Android.

Regardless, staying up to date on security patches is the best line of defense, and sandboxing everything is the next line. GrapheneOS provides both.

...on Google hardware with proprietary "security" chips that it refuses to open up. And Graphene's embargo patch Google partnership is shady. Why is it the only custom Android build to get this? Any unrevealed links to Google hidden from all of us? Because Micay loves creating toxic social media army, using sockpuppet trolling tactics evidently and obscuring or hiding conflict of interest.

"security by obscurity"

Ok, you lost me here. What they're providing is security by layers (sandboxing, reducing attack surface by having less stuff running, etc) and rapid security updates from upstream.

Google has one extra proprietary "security" hardware layer than every other Android phone in existence. This makes Google much more proprietary and unpredictable, which makes it logically unfit for adopting for privacy, security and anonymity purposes.