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

§6.1. Steps to generate authenticator data should include BE and BS flags #2064

Closed
emlun opened this issue Apr 30, 2024 · 3 comments · Fixed by #2141
Closed

§6.1. Steps to generate authenticator data should include BE and BS flags #2064

emlun opened this issue Apr 30, 2024 · 3 comments · Fixed by #2141
Assignees
Labels
@Risk Items that are at risk for L3 type:editorial
Milestone

Comments

@emlun
Copy link
Member

emlun commented Apr 30, 2024

Proposed Change

§6.1. Authenticator Data defines a procedure "Authenticators perform the following steps to generate an authenticator data structure", which includes the step:

This step, or perhaps a new subsequent step, should also reference setting the BE and BS flags.

@emlun
Copy link
Member Author

emlun commented Apr 30, 2024

Related: #2063

@nadalin nadalin added this to the L3-WD-02 milestone May 15, 2024
@zacknewman
Copy link
Contributor

zacknewman commented May 15, 2024

Just want to make sure that SHOULD is used instead of SHALL if it's not required for RPs to enforce that BE and BS are not 0 and 1 respectively. As the linked issue explains, the RFU bits are not supposed to be enforced to be 0; however Authenticators perform the following steps to generate an authenticator data structure mistakenly states they SHALL (i.e., MUST) be 0.

@emlun
Copy link
Member Author

emlun commented May 27, 2024

It is correct that authenticators SHALL set the RFU bits to zero, but as discussed in #2063 (comment), RPs should not enforce this as that would break those RPs if these bits are allocated in the future (unless the RP wants that breakage to happen, of course).

@nadalin nadalin added the @Risk Items that are at risk for L3 label Jul 31, 2024
@timcappalli timcappalli assigned timcappalli and unassigned emlun Jul 31, 2024
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.

4 participants