You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Webauthn attestation should be an explicit choice #264
Currently if the RP requests attestation and the authenticator supplies it, it's included in the response. Ideally this is something the client explicitly confirms they want. I suggest:
Always default to setting CTAP's attestationFormats = ["none"].
Only if the RP sets attestation = "direct":
Show a credentialsd-ui toggle to the user whether they want to include attestation that defaults to off
Only if the user enables it, forward the webauthn attestationFormats setting over CTAP.
This is a good direction. we should consider how this behavior might change between browsers and ordinary apps. Browsers may already draw their own UI to prevent this. If we do this ourselves, we should make sure to coordinate with browsers if that's OK with them, or add an option to allow browsers only to say that "I already showed attestation UI, continue without further prompts," similar to what we need to do for related origins.
Activity
[-]Attestation should be an explicit choice[/-][+]Webauthn attestation should be an explicit choice[/+]iinuwa commentedon Nov 13, 2026
This is a good direction. we should consider how this behavior might change between browsers and ordinary apps. Browsers may already draw their own UI to prevent this. If we do this ourselves, we should make sure to coordinate with browsers if that's OK with them, or add an option to allow browsers only to say that "I already showed attestation UI, continue without further prompts," similar to what we need to do for related origins.