Closed marcoscaceres closed 1 year ago
Looks like itβs in scope for the new WebAppsSec charter: https://www.w3.org/2021/06/webappsec-proposed-charter-2021.html#scope
So, perfect timing! π
@mikewest - thoughts on the above?
Looks like itβs in scope for the new WebAppsSec charter
Proposed charter, modulo some formal objections.
But yes. This proposal was explicitly on my mind (as well as something like https://github.com/tQsW/webcrypto-curve25519/blob/master/explainer.md) when adding that to the proposal. I think WebAppSec is a fine place for the work.
/cc @dveditz @samuelweiler @sideshowbarker in case they have different recollections.
/cc @dveditz @samuelweiler @sideshowbarker in case they have different recollections.
I believe your recollection is corrected
Also, heads-up to @twiss on this
Great. Once we have the charter situation resolved, I'm happy to help move this over. Just ping!
@twiss question for you, when the charter is resolved, would you prefer that this is landed as a new specification referencing Web Cryptography, or as an addition to the spec?
I would somewhat prefer to add it to the existing spec - I think since getRandomValues
and randomUUID
are quite closely related it would seem nice to have them in the same spec (and e.g. the security and privacy considerations overlap).
@twiss would you like me to start a straw person proposal against webcrypto?
Yeah, I would say go for it :+1:
Yeah, I would say go for it π
@twiss done https://github.com/w3c/webcrypto/pull/285 π
Chrome's web standards team is doing a minor project to clean up Googler-led incubations that have graduated or become inactive. Since this spec has successfully graduated, I've posted a few PRs to reflect that.
After they are merged, we should also update https://github.com/WICG/admin/blob/gh-pages/biblio.json , and then archive this repository.
Going ahead and archiving this repository. Further work should be taken up over in https://github.com/w3c/webcrypto/ (with potential new ideas incubated in the WICG with a new repo.)
As this spec is now widely implemented (Chromium, WebKit, Gecko), it would be nice to migrate it to a working group.
@WICG/chairs, could you kindly help us find a home for it?