search

w3c / webcrypto

The W3C Web Cryptography API
https://w3c.github.io/webcrypto/
Other
265 stars 54 forks source link

UUID generation as part of crypto.subtle? #215

Closed littledan closed 3 years ago

littledan commented 5 years ago

uuid is a very widely used package on npm for generation of RFC 4122 UUIDs. Would it make sense to add this to the web platform, in the interest of reducing download sizes?

UUIDs aren't intended to be treated as having security properties (e.g., depending on uniqueness), but RFC 4122 uses cryptographic algorithms. The uuid package uses WebCrypto's random number generation and SHA-1 implementation. For this reason, I thought it might make sense to expose it on the SubtleCrypto interface.

The usage could look something like this:

let uuid = await crypto.subtle.generateUuid({ algorithm: "v1" });

That options bag could have additional values for v3/v5 to specify a URL and namespace.

If enough browsers support the feature to reduce the need to ship the current package, then the uuid package could significantly reduce its bundle size on the web, maybe saving a bit less than 1k on a page load for pages that use UUIDs.

cc @developit

sideshowbarker commented 3 years ago

@littledan We seem to have mixed signals from web developers on whether they’d like to see this proposal implemented in browser engines. And we also don’t seem to have any browser-engine implementors who have weighed in with opinions either way. Do you have any plan on getting some implementors engaged here in discussion about this proposal? Otherwise, lacking any implementor engagement, and given it’s been open for two years, it seems like nothing’s going to happen with it.

ctavan commented 3 years ago

@sideshowbarker we have moved this effort into https://github.com/WICG/uuid/

Node.js has implemented the current API with v15.6.0, see https://nodejs.org/api/crypto.html#crypto_crypto_randomuuid_options

@bcoe may have additional information regarding implementation in Chromium.

sideshowbarker commented 3 years ago

@sideshowbarker we have moved this effort into WICG/uuid

OK, cool, thanks — that’s great, and I now recall seeing that (I just didn’t make the connection…)

But given that, do we need to also keep this issue open here?

ctavan commented 3 years ago

From my point of view we can close this and continue with the WICG effort.

sideshowbarker commented 3 years ago

OK @ctavan thanks — closing per https://github.com/w3c/webcrypto/issues/215#issuecomment-769889390