• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle


  • Android supports multiple payment providers. Some banks implement their own payment provider (e.g. Sparkasse in Germany), most just rely on Google Pay (now Google Wallet). Google Wallet has strict requirements for the Play Integrity API. Because of the modifications to Android that GrapheneOS is implementing, it is not eligible to receive the required integrity attestation and thus, Google Wallet is refusing to work. Google could at any point reconsider and certify/whitlelist GrapheneOS, which would allow Google Wallet to work using GrapheneOS. Likelihood close to 0.

    Any banking app implementing their own payment provider is completely independent of this decision unless it also relies on Play Integrity API attestation (or a similar mechanism).




  • This feels more like a hack than a suitable solution. Also, it does not work with static binaries.

    It would be nice to have better support for 464xlat clat on linux. Sure, there are implementations like clatd based on tayga (which, by the way, was last updated in 2011???) or jool (out-of-tree kernel module), but setting them up is rather cumbersome. On Android, I automatically get a v4-rmnet0 interface when I connect to an IPv6 only network (such as my mobile network), which provides a local IPv4 gateway for legacy applications and websites, that will automatically do nat64/clat. Prefix-discovery is done using DNS64.