Open
Bug 1096777
Opened 10 years ago
Updated 2 years ago
Properly handle JWK keys that have "oth" populated
Categories
(Core :: Security, defect)
Core
Security
Tracking
()
NEW
People
(Reporter: rbarnes, Unassigned)
References
(Blocks 1 open bug)
Details
If a JWK includes an "oth" field, then its modulus has more than 2 prime factors. In this case, using the "p", "q", "dp", "dq", etc. elements -- anything besides "n", "e", and "d" -- results in incorrect operation. Unfortunately, the current WebCrypto implementation does exactly this.
NSS doesn't support multi-prime, and doesn't accept private keys that have only "n", "e", and "d", so we need to update CryptoKey::PrivateKeyFromJwk to reject keys that include "oth".
|
Reporter | |
Updated•10 years ago
|
Blocks: web-crypto
|
||
Updated•9 years ago
|
Component: DOM: Security → Security
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•