nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqpygx5exzdwj8vpv2vey6qdt03xvsq4rn8ljj7hqy263hnzntqtzsxcuwp2 If they insist on verifying device/OS integrity, then they need to read https://grapheneos.org/articles/attestation-compatibility-guide which explains how they can use hardware attestation to verify GrapheneOS and permit it. They should also be made aware that the Play Integrity API has no actual security standards and permits devices with no security patches for a decade. They're permitting incredibly insecure devices but not hardened devices with GrapheneOS.

Reply to this note

Please Login to reply.

Discussion

nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqpygx5exzdwj8vpv2vey6qdt03xvsq4rn8ljj7hqy263hnzntqtzsxcuwp2 What they're doing demonstrates a near total lack of understanding security, which is quite concerning for a financial service. They think it's fine to go a decade without applying any security patches but somehow running a highly private and secure open source OS which has high hardware security standards only currently provided by Pixels is a problem for them. It doesn't make any sense. They need to educate themselves.

That's what I said, but they keep repeating the same line about ensuring consistent security standards across all users.

They don't understand security. They don't care about security.

... so now it's up to us to demonstrate that we do.