Re: [webauthn] Authenticator data flags reserved bits must be 0 or the figures would ideally be changed (#2063)

Interesting, so [CTAP 2.2](https://fidoalliance.org/specs/fido-v2.2-rd-20230321/fido-client-to-authenticator-protocol-v2.2-rd-20230321.html#u2f-authenticatorMakeCredential-interoperability) would seem to to align with the figures and not `flags` documentation as it says, "let flags be a byte whose zeroth bit (bit 0, UP) is set, and whose sixth bit (bit 6, AT) is set, and all other bits are zero (bit zero is the least significant bit)". This would suggest that `flags` should be updated to not only state the bits are "reserved for future use" but that in the meantime they must be 0.

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


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

Received on Monday, 29 April 2024 22:08:03 UTC