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
{{ message }}
Repository navigation
crypto: deduplicate and canonicalize CryptoKey usages - #62902
This was way more fun to track down than I expected.
The usage intersection operation requires the resulting [[usages]] slot to contain "each recognized key usage value that appears in both a and b, in the order listed in the list of recognized key usage values. This mandates both deduplication and a canonical ordering that is independent of the input order.
list of recognized key usage values and hence the canonical order is in W3C Web Cryptography API Level 2
This was way more fun to track down than I expected.
The usage intersection operation requires the resulting
[[usages]]slot to contain "eachrecognized key usage valuethat appears in both a and b, in the order listed in thelist of recognized key usage values. This mandates both deduplication and a canonical ordering that is independent of the input order.list of recognized key usage valuesand hence the canonical order is in W3C Web Cryptography API Level 2And then further overloaded by Modern Algorithms in the Web Cryptography API to be
Fixes: #62899