←back to thread

452 points akyuu | 1 comments | | HN request time: 0.212s | source
Show context
derbOac ◴[] No.45766747[source]
They couldn't answer the question most on my mind: "We’ve reached out to Google to inquire about why a custom ROM created by volunteers is more resistant to industrial phone hacking than the official Pixel OS. We’ll update this article if Google has anything to say."
replies(10): >>45766778 #>>45777056 #>>45778032 #>>45778056 #>>45779079 #>>45779102 #>>45779404 #>>45780503 #>>45781099 #>>45783125 #
LoganDark ◴[] No.45778032[source]
GrapheneOS makes security trade-off that are inconvenient to the user. This results in a far more secure device, but nonetheless a device that the general public would find far more annoying. Google would lose a proportion of its user base by implementing the same protections.

Example: https://old.reddit.com/r/GooglePixel/comments/ytk1ng/graphen...

Also Google Pay is missing.

replies(4): >>45778078 #>>45779111 #>>45779935 #>>45780063 #
tranq_cassowary ◴[] No.45779111[source]
Google Wallet works but tap-to-pay NFC payments don't because Google enforces strong Play Integrity for that portion. They only allow Google certified OSes to use it. It's a sad choice on their part, not GrapheneOS' fault or choice.
replies(1): >>45779164 #
LoganDark ◴[] No.45779164[source]
Without Google Pay, Google Wallet is practically a glorified card number vault. Which can still be useful, just not at card terminals.
replies(2): >>45779312 #>>45781781 #
1. subscribed ◴[] No.45781781[source]
Close.

To me it's a biggest missing feature to date (and the team brought that up with European Commission already, as there are no technical or security reasons for that). Worth noting it will work on the old, unpatched, rooted, wildly unsafe phones with the right magisk configuration. But not on the safest os.

Anyway, it keeps the passes okay for me, and for the payments I use Garmin Pay.