tranq_cassowary

8 ms·

61.
by tranq_cassowary 1y ago
The face unlock is deliberately left out. Non-EOL Pixel hardware, the only currently support phones, don't have the hardware to support secure face unlock. They lack the sensors. Face unlock on current Pixels is not secure and should b
62.
by tranq_cassowary 1y ago
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
63.
by tranq_cassowary 1y ago
Those honeypot phones clearly use marketing aimed at criminals and make all sort of false promises and clearly aren't technical and transparent projects like GrapheneOS. GrapheneOS community doesn't tolerate discussion of crime or
64.
by tranq_cassowary 1y ago
All of the listed features significantly raise the bar for exploitation ; https://grapheneos.org/features
65.
by tranq_cassowary 1y ago
GrapheneOS isn't made by volunteers. They have a team of around 10 paid developers. They are a nonprofit foundation that receives donations and uses those to pay developers, infrastructure etc. Ars Technica has update its article to re
66.
by tranq_cassowary 1y ago
That's because the OS integration is priviliged and that's problematic. On GrapheneOS Play runs sandboxed, like any other user-installed app.
67.
by tranq_cassowary 1y ago
That only turns it of on the OS level. GrapheneOS also turns it off on the level of the USB controller.
68.
by tranq_cassowary 1y ago
The reasoning is explained here: https://grapheneos.org/faq#device-support Note that Google is in active talks with an major Android OEM for a few months already to help them meet the requirements for a subset of their futu
69.
by tranq_cassowary 1y ago
If you have evidence of a hardware backdoor, please provide it. Otherwise you are just speculating and that doesn't bring value to a HackerNews discussion. Burden of proof lays upon you. GrapheneOS doesn't advocate use of Tor. See
70.
by tranq_cassowary 1y ago
If you are going to use a desktop instead, you are hurting your security significantly. Traditional desktop OSes like Window, MacOS and Linux desktop lack a sane security model with a mandatory app sandbox with fine-grained permissions. The
71.
by tranq_cassowary 1y ago
If you disallow Network permission to an app (a GrapheneOS feature), local network access is also disabled.
72.
by tranq_cassowary 1y ago
You can use Seedvault to make and restore a backup. Set up a secondary user profile with settings only (no apps yet), make a backup and use that in future for initializing other profiles. There are apps like Inter Profile sharing (appID: di
73.
by tranq_cassowary 1y ago
It's not really like having multiple phones. User profiles are a useful features, also for privacy, but they are not a privacy or security silver bullet. Within any given user profile, apps are sandboxes. An app can't peak into th
74.
by tranq_cassowary 1y ago
The planned sideloading instructions only apply to certified OSes. GrapheneOS is not certified because it doesn't bundle privileged Google Mobile Services.
75.
by tranq_cassowary 1y ago
Sandboxed Google Play doesn't really defeat the point of GrapheneOS. Not wanting to use Google Play or any proprietary Google services is perfectly valid, for all clarity. But, it's just important to note that for people that hea
76.
by tranq_cassowary 1y ago
This blogpost is highly inaccurate and a heavy misportrayal of the events that occured. The title is completely wrong already. They did not get banned from GrapheneOS. GrapheneOS is a free and open source operating system, you can’t be bann