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

FIDO Issue Collection #382

Open
My1 opened this issue Feb 21, 2023 · 2 comments
Open

FIDO Issue Collection #382

My1 opened this issue Feb 21, 2023 · 2 comments

Comments

@My1
Copy link
Contributor

My1 commented Feb 21, 2023

A mix of Bugs and Feature Reqs relevant to FIDO2 to keep everything together on a list

Bugs:
#380 - Bruteforce Protection problematic with allow/exclude lists of credentials for login and registering (ca. 3 sec per entry, seems to force fail after 5+ entries.)

Ideas:
CTAP2.1-related
#353 - CredProtect extension (e.g. required by Resident Key Option in OpenSSH)
#304 - hmac-secret for Secret exchange (e.g. AAD or fido2luks) (not a CTAP2.1 thing per se but needed for CTAP2.1 specification)

#378 - set FIDO counter to always be zero for new setups to remove the need for time or other methods of keeping a counter

Not yet Listed - non-resident Keys: removes the need to constantly sync Database between multiple MPs

Discussion/clarify:
#265 - my view so far is that as the MP currently does not use attestation certs, this is not yet relevant but will become important if/when attestation certs become a thing
#175 - explore the validity of silent Auth outside Webauthn. -> https://fidoalliance.org/specs/fido-v2.1-rd-20210309/fido-client-to-authenticator-protocol-v2.1-rd-20210309.html#op-getassn-step-sign mentions only that up=0 is invalid at the webauthn layer, however if 378 is implemented this will become moot.
#225 - Possibly add notes to manual or other documentation about skipping sending attestation

@My1 My1 changed the title FIDO Enhancement Collection FIDO Issue Collection Feb 21, 2023
@limpkin
Copy link
Contributor

limpkin commented Feb 21, 2023

oh thanks for that :)

@My1
Copy link
Contributor Author

My1 commented Feb 21, 2023

no problem. I think it's useful to have a quick list what's there to fix/add/discuss incl. quick explanations why

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

2 participants