Closed
Bug 1851719
Opened 2 years ago
Closed 2 years ago
Avoid using CryptoBuffer / fallible allocator for authenticator provided data in WebAuthn
Categories
(Core :: DOM: Web Authentication, enhancement, P3)
Core
DOM: Web Authentication
Tracking
()
RESOLVED
FIXED
119 Branch
Tracking | Status | |
---|---|---|
firefox119 | --- | fixed |
People
(Reporter: jschanck, Assigned: jschanck)
Details
Attachments
(1 file)
CryptoBuffer
is a FallibleTArray<uint8_t>
with some helper functions for conversions to/from other types. Using a fallible allocator adds little value when we're handling trusted outputs from the user's authenticator. We should avoid CryptoBuffer when we're handling data that is 1) known to be small and/or 2) coming from a trusted source.
Assignee | ||
Updated•2 years ago
|
Type: task → enhancement
Assignee | ||
Comment 1•2 years ago
|
||
Pushed by jschanck@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/504bc16acc75
avoid using CryptoBuffer for authenticator provided data. r=keeler
Comment 3•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox119:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•