You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(pin): require exact pinUvAuthToken length per protocol
The boundary check accepted any token of at least min_token_len bytes,
so protocol one accepted e.g. a 20-byte token and protocol two a
33-byte one. CTAP 2.1 requires the decrypted pinUvAuthToken to be
exactly 16 or 32 bytes for protocol one and exactly 32 bytes for
protocol two. Replace the minimum-length check with an exact-length
helper and unit-test it.
0 commit comments