Normalize usage list in generateKey operations - #557
Conversation
Found from the recent changes (web-platform-tests/wpt#61397) in WPT tests. For the generateKey operations of symmetric key algorithms (AES-CTR, AES-CBC, AES-GCM, AES-KW and HMAC), we should normalize the usage list assigned to the [[usages]] internal slot of the new CryptoKey. Note that, for the generateKey operations of asymmetric key algorithms (RSASSA-PKCS1-v1_5, RSA-PSS, RSA-OAEP, ECDH, ECDSA, Ed25519 and X25519), the usage lists assigned to the [[usages]] internal slot of the new CryptoKey are already normalized by the usage intersection (https://w3c.github.io/webcrypto/#concept-usage-intersection). Signed-off-by: Kingsley Yung <kingsley@kkoyung.dev>
twiss
left a comment
There was a problem hiding this comment.
Thanks for the PRs! Could you please either join the WebAppSec and WICG groups, or mark your PRs as non-substantive?
|
kkoyung marked as non substantive for IPR from ash-nazg. |
I'm not an employee of any W3C member organization. It seems I need to get some approval to join the groups, which will take time. Perhaps it would be simpler to just mark the PRs as non-substantive. |
Found from the recent changes (web-platform-tests/wpt#61397) in WPT.
For the generateKey operations of symmetric key algorithms (AES-CTR, AES-CBC, AES-GCM, AES-KW and HMAC), we should normalize the usage list assigned to the [[usages]] internal slot of the new CryptoKey.
Note that, for the generateKey operations of asymmetric key algorithms (RSASSA-PKCS1-v1_5, RSA-PSS, RSA-OAEP, ECDH, ECDSA, Ed25519 and X25519), the usage lists assigned to the [[usages]] internal slots of the new CryptoKey are already normalized by the usage intersection (https://w3c.github.io/webcrypto/#concept-usage-intersection).
Preview | Diff