Open plehegar opened 4 years ago
We're also investigating a separate proposal for bringing part of the WebCrypto API into ECMA-262 at https://github.com/tc39/proposal-csprng, which would possibly replace the Math.getRandomValues()
part of the UUID proposal. In particular, there are several open issues I'd like to get feedback on from the WebCrypto WG:
I'm also interested in other general feedback in the approach outlined in https://github.com/tc39/proposal-csprng/pull/2, which amends the CSPRNG proposal to adopt the global crypto
namespace in a way to be (hopefully) compatible with the WebCrypto API.
Note that the WG closed back then. However, there are ongoing discussion to do something. See also https://github.com/w3ctag/design-reviews/issues/466
This would essentially be an editorial change, right? I mean, no implementation impact?
This issue is meant to track the conversation at: https://github.com/tc39/proposal-uuid/pull/33
If getRandomValues is upstreamed in ECMA-262, we should update the Web Crypto API to reference their definition (assuming it's compatible).