Issue metadata
Sign in to add a comment
|
U2fSign and U2fRegister should have a specific U2fResponseCode for duplicate registrations |
||||||||||||||||||||||||
Issue descriptionU2fSign and U2fRegister seem to be repurposing CONDITIONS_NOT_SATISFIED to mean duplicate registration, whereas, internally, it used to indicate almost the opposite: the user did not touch the device (no user consent), even though the operation at hand would have succeeded if the user did The operations should return something specific to duplicate registrations. https://cs.chromium.org/chromium/src/device/fido/u2f_sign.cc?l=72 https://cs.chromium.org/chromium/src/device/fido/u2f_register.cc?l=134
,
Mar 30 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kpaulhamus@chromium.org
, Feb 28 2018