Daniel Micay

It's referring to what Brave and Firefox are doing for their cookie partitioning.

Don't know, but you can try https://web.dev/articles/cross-origin-isolation-guide enabling the background sync feature in site settings. It's probably expected due to the settings.

@arnar Android key attestation has an older approach based on either a provisioned batch key (unprivileged apps) or unique key (privileged OS components only). The mandatory 100k+ device batch keys...

We intend to eventually have our own device which would use our own attestation root both for the TEE and secure element keystores along with providing our own implementation of...

The Google Play implementation can be used with our sandboxed Google Play compatibility layer (https://grapheneos.org/usage#sandboxed-google-play) and there are apps with standalone implementations including https://play.google.com/store/apps/details?id=de.cotech.hw.fido.browser. It's very unfortunate that it's not...

There **are** some UX issues with some parts of FIDO2 via the sandboxed Google Play compatibility layer since it **does** use privileged access on the stock OS for various parts...

Password can be any Unicode characters but the username has to be the 26 letter Latin alphabet and numbers.

Can you rebase this?

This is due to the Vanadium Library which isn't a regular app and currently needs very special handling due to Android not allowing using regular APIs for it.

> A highly customisable firewall with per-app and per-network configuration is obviously preferred. That would be incredibly leaky without treating network access as disabled and allowing only specific cases which...