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

Clarify which sign. algm.'s RP's must support (Sec. 4.3.2.1.2) #104

Closed
gmandyam opened this issue May 13, 2016 · 2 comments
Closed

Clarify which sign. algm.'s RP's must support (Sec. 4.3.2.1.2) #104

gmandyam opened this issue May 13, 2016 · 2 comments

Comments

@gmandyam
Copy link

Current text states "The following algorithms must be implemented by servers:" and goes on to list target signing methods. But the text later says "WebAuthn Relying Parties must implement all the algorithms implemented by the authenticators that they support."

The two statements seem to contradict each other. For instance, if an RP does not support any authenticators that implement ECDAA then it does not seem to be necessary for the RP to implement ECDAA. Would recomment changing "The following algorithms must be implemented by servers:" to "One or more of the following algorithms must be implemented by servers (depending on the authenticators that servers support):"

@vijaybh vijaybh added this to the CR milestone May 13, 2016
@equalsJeffH
Copy link
Contributor

equalsJeffH commented May 21, 2016

at the time @gmandyam submitted this issue, S 4.3.2.1.2 mapped to this spot in index.src.html: {#packed-attestation-signature}. we need to note such spec source anchors in issues because section #s will change over time as we move sections around.

@vijaybh
Copy link
Contributor

vijaybh commented Sep 16, 2016

We already decided in Berlin to not specify server behavior in this spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants