Re: [webauthn] "android-key" and "android-safetynet" are really basic attestation type support? (#1819)

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 available as part of an Android mainline module. The way that mainline modules are developed separately from the AOSP monthly/quarterly/yearly releases is also frustrating for us, since it would be extremely inconvenient to make 20 different AOSP source trees with our changes applied to build the latest release of each mainline module instead of building the version currently in AOSP. It would be nice if AOSP was developed as more of a proper open source project considering the needs of more than Google certified releases with Google Play, just as it would be nice if Chromium was more collaborative. AOSP has much less open and collaborative developer than Chromium though, due to them keeping the sources for upcoming releases private. That also leaks into Android Chromium not being as openly developed where sometimes they forget to land things 'upstream' (in Chromium).

-- 
GitHub Notification of comment by thestinger
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1819#issuecomment-1516323917 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 20 April 2023 13:23:44 UTC