Clarify attestation wrt passkeys

Open
#46,142 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Domain
documentation

Research direction

The question is whether the Passkeys guide's attestation section should state that attestation is a non-goal for passkeys, and this needs a maintainer decision and a spec source before any edit. Start by reading the attestation section of the linked Passkeys guide and checking the WebAuthn and passkey specifications for the claim. Done means a documented, sourced answer agreed with the maintainers, not a rewrite of the page.

Written by the indexing model from the issue text.

Description

Content:Security needs triage

https://hachyderm.io/@rmondello/117428258722253709 says that attestation is "an explicit non-goal" for passkeys. Our guide does have a section on attestation, but it doesn't give anything like this guidance.

Is there a definitive spec or even guide document for passkeys, that could provide an answer in cases like this?

https://github.com/mdn/content/issues/45753 is related but different, as that issue is about WebAuthn, which of course might have different applications in mind, including some that might require attestation.

Dominant language
Markdown
Stars
11.1k
Forks
23.3k
Avg merge
2d 12h
Merged PRs (30d)
187

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mdn/content

All issues in mdn/content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.