Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
strcat
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
25 ms
·
301.
▲
by
strcat
1y ago
Most banking apps don't disallow GrapheneOS. A growing subset are banning using any alternate OS including GrapheneOS, but there's also progress on convincing those apps to permit GrapheneOS via hardware attestation. Most banking
302.
▲
by
strcat
1y ago
You can use most banking apps on GrapheneOS but a subset block using any alternate OS. GrapheneOS supports hardware attestation and some banking apps explicitly permit GrapheneOS via hardware attestation such as Swissquote which recently ad
303.
▲
by
strcat
1y ago
It also has the caveat that protecting against privileged attacker persistence doesn't work by definition, so it only provides protection against physical attacks. The protection against physical attacks is also reduced through having
304.
▲
by
strcat
1y ago
Official support for Google Messages on GrapheneOS is being developed instead of needing to set it up in a very particular way where it can be fragile. In the long term, we plan to make our own RCS app.
305.
▲
by
strcat
1y ago
Private Space is from Android 15 so GrapheneOS has provided support for it since October 2024 when Android 15 was released. Profiles are a standard Android feature, not something added by GrapheneOS, and are not required to benefit from the
306.
▲
by
strcat
1y ago
GrapheneOS provides much better privacy, stability and app compatibility than /e/ rather than only security. GrapheneOS entirely exists as a privacy project and focuses on security too in order to protect privacy. GrapheneOS is a
307.
▲
by
strcat
1y ago
It's important to note that user profiles are a standard Android feature, as are Private Space and work profiles nested within the Owner user. None of the core privacy and security features of GrapheneOS require using user profiles. We
308.
▲
by
strcat
1y ago
> It's incredibly and unjustifiably inflexible and treats the user like they're the primary security threat. There are no restrictions on what people can do added by GrapheneOS compared to the Android Open Source Project /
309.
▲
by
strcat
1y ago
Curve Pay also works, as do European banks using the standard approach not dependent on Google Play. Tap-to-pay is not an issue for GrapheneOS users in the UK and EU.
310.
▲
by
strcat
1y ago
See the response at https://news.ycombinator.com/item?id=45244398 .
311.
▲
by
strcat
1y ago
See the response at https://news.ycombinator.com/item?id=45244398 .
312.
▲
by
strcat
1y ago
See the response at https://news.ycombinator.com/item?id=45244398 .
313.
▲
by
strcat
1y ago
See the response at https://news.ycombinator.com/item?id=45244398 .
314.
▲
by
strcat
1y ago
QubesOS provides strong compartmentalization between virtual machines defined by the user, but it doesn't provide better protection against exploitation within those guests. Network drivers are a special case due to running in a dedica
315.
▲
by
strcat
1y ago
It's worth noting they're still regular sandboxed apps regardless of whether you use dedicated profiles for this. The main reason to use a separate profile for this is for fine-grained control over which apps can/will use Goo
316.
▲
by
strcat
1y ago
> but location data etc still goes to them No, they can be installed as regular sandboxed apps and you don't need to grant them any of the standard permissions such as Location. They have the same app sandbox and permission model as
317.
▲
by
strcat
1y ago
Private Spaces are available since Android 15 and provides a similar nested profile without the need for a management app. They're better integrated into the OS user interface. Secondary users, work profiles and Private Spaces are stan
318.
▲
by
strcat
1y ago
We would happily support other devices meeting these requirements and have limited what we include in the requirements to enable that. We're actively working with a major OEM towards a subset of their devices meeting these standards an
319.
▲
by
strcat
1y ago
We're actively working with a major Android OEM since June 2025 towards a subset of their future devices meeting our requirements. They've been interested in improving their security for a while and have demands for it from large
320.
▲
by
strcat
1y ago
It was never a hardened OS in the same space as GrapheneOS. https://eylenburg.github.io/android_comparison.htm provides a good overview. It was much more similar to LineageOS and various LineageOS-based operating systems.
321.
▲
by
strcat
1y ago
We haven't removed any requirements from our list. Many things Pixels provide are omitted from the list in order to enable another device to meet our requirements. There are other devices meeting the security feature requirements, but
322.
▲
by
strcat
1y ago
> Waydroid can run Android apps. Waydroid has a very outdated fork of Android with the privacy/security model largely disabled. It has poor Android app compatibility. The apps are no longer isolated from each other and the kernel is
323.
▲
by
strcat
1y ago
Both of these are closed source hardware with closed source firmware. Neither is an open hardware device. They're extremely far from meeting the official requirements for GrapheneOS. It would not be GrapheneOS with massive portions of
324.
▲
by
strcat
1y ago
No, it's not resistant to forensics unless it's turned off when obtained. The hardware / firmware / software makes no serious attempt to protect a device in the After First Unlock state.
325.
▲
by
strcat
1y ago
GrapheneOS only supports devices where users can have full control over the OS and replace it. Choosing to use GrapheneOS is fully optional and people who don't want a strong security model can use something else. Not clear how Graphen
326.
▲
by
strcat
1y ago
GrapheneOS is for people who want highly private and secure mobile devices. It has a very reasonable set of security requirements for hardware listed at https://grapheneos.org/faq#future-devices . Other devices meeting these
327.
▲
by
strcat
1y ago
GrapheneOS has to do substantial work on each supported device to integrate the hardening features and fix the issues those uncover. Supporting other devices is not easy and involves a lot of resources. Those devices also need to provide th
328.
▲
by
strcat
1y ago
See the relevant part of the response in https://news.ycombinator.com/item?id=45229295 .
329.
▲
by
strcat
1y ago
> This is another project that knows what you need better than yourself. People are constantly asking them to add support to other hardware, but the answer is "it's insecure". This is completely wrong and forces everybody
330.
▲
by
strcat
1y ago
CalyxOS was not a hardened OS and is a much different space from GrapheneOS. https://eylenburg.github.io/android_comparison.htm provides a high quality comparison of the privacy and security between different alternate AOSP
More ›