Frage an euch: Viele zögern, #GrapheneOS zu installieren, obwohl es eigentlich recht einfach ist. Wie wäre es, wenn der Kuketz-Blog eine Dienstleistung anbietet, die die Installation gegen eine Aufwandsentschädigung von etwa 50 € übernimmt? Was denkt ihr – gäbe es dafür Interesse?

#android #datenschutz #privacy #customrom

Ja
36%
Nein
32.8%
Keine Ahnung
31.1%
Poll ended at .

@kuketzblog

"Im Prinzip" würde ich so einen Service gerne nutzen, auch wenn ich's selber flashen könnte (Stress, Arbeitszeit sparen).

Dass ich nicht #GrapheneOS verwende liegt an der Zwickmühle, dass nur die Google Pixels derzeit die nötige Sicherheitshardware dafür mitbringen und ich mich nicht so recht überwinden kann, ausgerechnet diesem Konzern Geld zu geben.

@katzenberger @kuketzblog Genau das gleiche Dilemma habe ich auch..

@BafDyce @katzenberger @kuketzblog

Eben. Ein Thema bei #GrapheneOS ist die Limitierung auf #Pixel-Geräte von #Google(!).

@nick Other Android devices do not have reasonable security. Our official security requirements are listed at https://grapheneos.org/faq#future-devices. Everything there is a very basic and reasonable requirement. No other Android OEM takes security seriously. The next best choice after GrapheneOS is an iPhone and non-Pixel Android devices are nowhere close. None even stops commercial exploit tools widely available to police from successfully brute forcing a PIN in Before First Unlock state.
GrapheneOS Frequently Asked Questions

Answers to frequently asked questions about GrapheneOS.

GrapheneOS
@nick Which Android OEM do you think has better practices than Google? The idea that Google is a uniquely bad company is quite strange and not aligned with the reality of for-profit companies focusing on maximizing their profit and the vast majority not taking security seriously or even compromising between their interests and user privacy to even the extent Google does. Storing a bunch of data for targeted ads and not adding enough E2EE options is far from below average.
@nick We aren't ever going to support insecure devices, so as long as other Android devices are insecure we're never going to be supporting them. It's not simply that they are less secure but flat out insecure without basic security features needed to protect people's privacy/security. A device where it's impossible for us to even protect users from very widely used exploits routinely used at borders, protests, etc. is not acceptable. We have security standards and they're reasonable.

@GrapheneOS @nick

Okay these are pseudo arguments.we know your point but this post is childish

@Underfaker @nick @kuketzblog

Information challenging your existing beliefs and preferences isn't a pseudo argument. What we wrote is accurate and logical. You're not engaging with what we wrote but rather are just making baseless jabs.

There's one more reasonable device choice for someone who cares a lot about privacy and security: an iPhone. Do you disagree?

Do you think there's another Android device with reasonable security and support for using an alternate OS? If you do, which one?

@Underfaker @nick @kuketzblog

We don't think there's even another Android device with a reasonable level of privacy and security, let alone one with remotely competitive security to an iPhone or Pixel. Do you disagree? If you agree with our position, what's the point of making the jabs towards us?

We aren't going to support an insecure device where we can't defend our users from real world attacks. Our security requirements get expanded based on improvements needed to keep up with attackers.