Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reference CTAP2.1 PS spec and fix broken link #1635

Closed
equalsJeffH opened this issue Jun 30, 2021 · 2 comments · Fixed by #2004
Closed

reference CTAP2.1 PS spec and fix broken link #1635

equalsJeffH opened this issue Jun 30, 2021 · 2 comments · Fixed by #2004
Assignees
Labels
@Risk Items that are at risk for L3 type:editorial
Milestone

Comments

@equalsJeffH
Copy link
Contributor

webauthn L2 Rec references the old CTAP v2.0-ps-20190130 spec, and thus the link to "large, per-credential blobs" does not work (the latter is a webauthn L2 Rec errata item (I dunno if it is worth fixing)).

we need to update the webauthn L3 working draft should link to https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html

the link to [=§6.2. Responses=] in the CTAP2.1 spec no longer works because we removed that entire section from the CTAP spec (doh). the two other links to the CTAP spec continue to work.

@equalsJeffH equalsJeffH added this to the L3-WD-01 milestone Jun 30, 2021
@equalsJeffH equalsJeffH self-assigned this Jun 30, 2021
@emlun emlun assigned emlun and unassigned equalsJeffH Oct 6, 2022
@nadalin nadalin added the @Risk Items that are at risk for L3 label Jun 27, 2023
@selfissued selfissued assigned selfissued and unassigned emlun Sep 12, 2023
@selfissued
Copy link
Contributor

PR #1961 fixed the first reference issue. I'll create a PR to fix the second one.

@plehegar plehegar modified the milestones: L3-WD-01, L3-WD-02 Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@Risk Items that are at risk for L3 type:editorial
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants