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

Either UV or UP should be enough #1037

Closed
yackermann opened this issue Aug 14, 2018 · 10 comments
Closed

Either UV or UP should be enough #1037

yackermann opened this issue Aug 14, 2018 · 10 comments
Assignees

Comments

@yackermann
Copy link
Contributor

The step 12 mandating in section 7.2 mandating UP:

Verify that the User Present bit of the flags in authData is set.

Some of the authenticators, such as smart cards, don't have UP. So in this case UV should be enough.

@sbweeden
Copy link
Contributor

I thought that UP was required to prevent silent authentications from being solicited via webauthn.

@apowers313
Copy link
Contributor

Some of the authenticators, such as smart cards, don't have UP. So in this case UV should be enough.

Depends on what you mean by "UP". They don't have a "button" dedicated to user presence, but their operation (tapping a NFC smart card to a reader, inserting a buttonless USB authenticator) does actually prove to a relying party that the user is present.

@emlun
Copy link
Member

emlun commented Aug 14, 2018

their operation (tapping a NFC smart card to a reader, inserting a buttonless USB authenticator) does actually prove to a relying party that the user is present.

I agree, but it's debatable whether a USB device left plugged in for an extended time (perhaps with a PIN cached for the session) should still be regarded as guaranteeing user presence.

@yackermann
Copy link
Contributor Author

@sbweeden UP or UV. If UV set to false, UP is request. V.V.

@selfissued
Copy link
Contributor

The table explaining UP/UV combinations at the end of https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html#authenticatorGetAssertion (right before https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html#authenticatorGetNextAssertion) may be helpful in considering this issue. It says:

Flags Meaning
"up"=0 "uv"=0 Silent authentication
"up"=1 "uv"=0 Physical user presence verified, but no user verification
"up"=0 "uv"=1 User verification performed, but physical user presence not verified (a typical "smartcard scenario")
"up"=1 "uv"=1 User verification performed and physical user presence verified

@nadalin
Copy link
Contributor

nadalin commented Aug 14, 2018

@herrjemand At this point i'm not sure anything needs to be done here

@sbweeden
Copy link
Contributor

sbweeden commented Aug 14, 2018

@nadalin The question is whether the guidance in the webauthn spec (that UP must ALWAYS be set in authenticate responses from the authenticator) is correct?

At the very least we need to make that determination.

@akshayku
Copy link
Contributor

At this moment, we don't allow silent authentication and every response has UP set. There is no scenario where UV is set and UP is not set. "Smart Card" scenario doesn't exist right now as platform has to look for user interaction before doing anything. So no change is required right now.

@nadalin
Copy link
Contributor

nadalin commented Aug 15, 2018

@herrjemand Discussed on call and closing no action

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

7 participants