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

Re: State of the WebCrypto API

From: Tony Arcieri <bascule@gmail.com>
Date: Mon, 12 Oct 2015 12:57:58 -0700
Message-ID: <CAHOTMVKJCCK5MZQNuMFG496iBkHygYLMTFLyR9SF8V1mQDK4RQ@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: "henry.story@bblfish.net" <henry.story@bblfish.net>, Carvalho Melvin <melvincarvalho@gmail.com>, "noloader@gmail.com" <noloader@gmail.com>, "public-web-security@w3.org" <public-web-security@w3.org>
On Monday, October 12, 2015, Anders Rundgren <anders.rundgren.net@gmail.com>
wrote:
>
> IE 11 is Microsoft's most recent browser for their currently largest
> installed base of Windows.
> Why does it still require a workaround?  Probably because there's limited
> demand for WebCrypto.
>

Anders,

I already explained this to you, but let's try again:

WebCrypto uses promises

IE11 does not support promises

Microsoft has no plans to add support for promises to IE11

You started  this thread by linking to this article, which
demonstrates Microsoft's commitment to WebCrypto in Edge:

https://msdn.microsoft.com/en-us/library/dn904640(v=vs.85).aspx

In other words, the technical basis to your argument runs diametrical to
your point (which is little more than instilling fear, uncertainty, and
doubt about WebCrypto)

Please stop posting threads like this. I can't tell if you're being
actively deceptive to malicious ends, or are truly incapable of
understanding the underlying concepts, but either way this has to stop.

To the chairs: threads like this discourage reasoned technical discussion
on this mailing list.

-- 
Tony Arcieri
Received on Monday, 12 October 2015 19:58:28 UTC

This archive was generated by hypermail 2.3.1 : Monday, 12 October 2015 19:58:29 UTC