Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
General discussion about devices is welcome. Please direct technical support, upgrade questions, buy/sell, app recommendations, and carrier-related issues to other communities.
"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.
@[email protected] @[email protected] 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.
@[email protected] @[email protected] 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.
Should I ever need lecturing wrt to Google I'll ask you for it.
Muted for 7 days.
@[email protected] @[email protected] Muting any information that's at odds with your beliefs/decisions is a strange thing to do when you're seeking out discussion about it by replying to a post this way. You could have marked the reply only for your followers and the author of the post if you didn't want discussion about it.
@katzenberger @kuketzblog Genau das gleiche Dilemma habe ich auch..
@[email protected] 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.
@BafDyce @katzenberger @kuketzblog
Eben. Ein Thema bei #GrapheneOS ist die Limitierung auf #Pixel-Geräte von #Google(!).
@nick @BafDyce @katzenberger Die Unterstützung eines anderen Herstellers würde _aktuell_ zulasten der Sicherheit gehen. Das wird GrapheneOS daher erst machen, wenn ein anderer Hersteller ein vergleichbares Sicherheitsniveau bietet: https://www.kuketz-blog.de/weshalb-grapheneos-aktuell-nur-google-pixel-geraete-unterstuetzt/
@mynacol
Das mit der angeblich besseren Sicherheit der Pixels kann ich nicht wirklich nachvollziehen. Auch Googles Geräte bringen proprietäre (Google (!), Qualcom, ...) BLOBs mit, auf die sich jedes OS stützen muss. Und dann hätten wir noch das Baseband. Da können überall hübsche Hintertüren versteckt sein, an denen das OS genau nichts retten kann. Man muss sich nur mal die Sicherheitsmitteilungen der FW-Hersteller ansehen.
@BafDyce @katzenberger @nick
@PC_Fluesterer @mynacol @BafDyce @katzenberger @nick Every ARM and x86_64 CPU is entirely closed source. CPU, GPU, MMU and everything else in them is closed source. This is not a negative or positive security property for this hardware but rather orthogonal to it. Even with reproducible builds, open source does not prevent a backdoor at all. That's clearly true based on the fact that unintentional, non-hidden critical vulnerabilities last for many years in open source projects. It's basic logic.