W3C home > Mailing lists > Public > public-web-security@w3.org > January 2015

Re: [W3C Web Crypto WG] Rechartering discussion

From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Thu, 08 Jan 2015 14:26:31 +0000
Message-ID: <54AE9397.5040408@cs.tcd.ie>
To: GALINDO Virginie <Virginie.Galindo@gemalto.com>, "public-webcrypto@w3.org" <public-webcrypto@w3.org>
CC: "public-web-security@w3.org" <public-web-security@w3.org>, Wendy Seltzer <wseltzer@w3.org>, Harry Halpin <hhalpin@w3.org>

I've no idea if this would be attractive to folks but
from my very limited initial uses of webcrypto I would
like it a lot if there were synchronous equivalents
for a lot of the functions. Making it all promises might
be nice but for many applications I know that I e.g.
only want to encrypt a key and forcing async code on
everyone for that is IMO undesirable. RSA key generation
is one where only having async seems reasonable but
there must be many operations where synchronous calls
would be as quick or quicker and would lead (again IMO,
and I'm not a JS expert or purist:-) to better code
structure.

S.

On 07/01/15 09:48, GALINDO Virginie wrote:
> Dear all,
> 
> Web Crypto WG charter [1] will end by the end of March. We need to prepare the next charter of Web Crypto.
> 
> As a reminder, the conversation has started on this page :   https://www.w3.org/Security/wiki/IG/webcryptonext_draft_charter
> Feel free to add you ideas and suggestions on the wiki and/or expose your opinion and question on the public-webcrypto@w3.org<mailto:public-webcrypto@w3.org> or public-webcrypto-comment@w3.org<mailto:public-webcrypto-comment@w3.org> (for non W3C Web Crypto WG members).
> 
> Regards,
> Virginie
> 
> [1] http://www.w3.org/2011/11/webcryptography-charter.html
> 
> ________________________________
> This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
> E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
> Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
> 
Received on Thursday, 8 January 2015 14:27:00 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 January 2015 14:27:00 UTC