- From: Richard Barnes <rbarnes@bbn.com>
- Date: Wed, 27 Feb 2013 15:11:49 -0500
- To: GALINDO Virginie <Virginie.GALINDO@gemalto.com>
- Cc: "'public-webcrypto@w3.org'" <public-webcrypto@w3.org>
I support closing this issue. As I read it, the API already allows multi-origin usage of keys, because keys are clonable. If that's not the case, then the document should specify that if keys are cloned across an origin boundary (e.g., through postMessage), then they will not work. But that seems like unnecessary complication. On Feb 25, 2013, at 11:38 AM, GALINDO Virginie <Virginie.GALINDO@gemalto.com> wrote: > Dear all, > > As mentioned in a previous mail, and in the spirit to progress on the Web Crypto API (Low Level), I would like to remind you that the multiple origin feature, as described in ISSUE-26 [1] is still awaiting for some proposals/contribution in the coming week. If there is no contribution, this feature will be put on hold and the ISSUE will be postponed, which means that our final deliverable might not embed any solution for it. > > Regards, > Virginie > Chair of the Web Crypto WG > [1] https://www.w3.org/2012/webcrypto/track/issues/26 >
Received on Wednesday, 27 February 2013 20:12:18 UTC