Skip to content

Normalize usage list in generateKey operations - #557

Merged
twiss merged 1 commit into
w3c:mainfrom
kkoyung:normalize-usages
Aug 6, 2026
Merged

Normalize usage list in generateKey operations#557
twiss merged 1 commit into
w3c:mainfrom
kkoyung:normalize-usages

Conversation

@kkoyung

@kkoyung kkoyung commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

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

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 twiss changed the title Normalize usage list in generateKey oeprations Normalize usage list in generateKey operations Aug 6, 2026

@twiss twiss left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PRs! Could you please either join the WebAppSec and WICG groups, or mark your PRs as non-substantive?

@w3cbot

w3cbot commented Aug 6, 2026

Copy link
Copy Markdown

kkoyung marked as non substantive for IPR from ash-nazg.

@kkoyung

kkoyung commented Aug 6, 2026

Copy link
Copy Markdown
Contributor Author

If you do not work for a W3C Member organization, first consider whether your employer can join W3C and get the benefits of Membership.

If this is not an option and you think that you have the expertise and availability to participate, you may request to participate as an Invited Expert as follows.
Note: Your application is subject to approval by the Chairs and Staff Contacts of this group. Please contact Simone Onofri to discuss your intent to complete an application before starting the process.

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.

@twiss
twiss merged commit 1ecb1af into w3c:main Aug 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants