W3C home > Mailing lists > Public > public-webcrypto@w3.org > May 2013

Re: ISSUE-26 is expecting proposal or will be postponed

From: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
Date: Wed, 8 May 2013 15:53:05 +0000
To: Richard Barnes <rbarnes@bbn.com>
CC: GALINDO Virginie <Virginie.GALINDO@gemalto.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
Message-ID: <23594B37-A619-48C6-AC5A-087FD21E6CD1@inventivegroup.com>
I thought that we already agreed that keys are structured clone-able across an origin boundary using postMessage.

Nick

On 27 Feb 2013, at 21:11, Richard Barnes <rbarnes@bbn.com> wrote:

> 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
>>
>
>
>
>


________________________________

Inventive Designers' Email Disclaimer:
http://www.inventivedesigners.com/email-disclaimer
Received on Wednesday, 8 May 2013 15:53:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:17 UTC