[Bug 25985] WebCrypto should be inter-operable

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25985

--- Comment #17 from Ryan Sleevi <sleevi@google.com> ---
(In reply to Web Cryptography Working Group from comment #14)
> Precisely, I think that is what we discussing doing as well - i.e. change
> "recommended" to "suggested" and then see how tough interop is doing CR. I'm
> not adverse to, if we get widespread interop during CR, to adding some
> algorithms as mandatory to be implement.

In case it hasn't been perfectly clear, I am strongly opposed to this and would
view it as a blocking issue.

I suspect that the Google team is the most unique, so far, in their WebCrypto
implementation. I'm not aware of Microsoft's mobile implementation plans.
Apple's plans in theory share the same implementation infrastructure
(CommonCrypto), but I do believe that the iOS implementation is slightly
different than the OS X (certainly has been the case for every one of their
previous APIs).

However, on the Chrome side, I'm daily dealing with a wide variety of hardware
and platforms. Our abilities on Windows (where we have chosen to deal with the
hassle of shipping crypto ourselves) are different than our abilities on Linux
(where we have not) than our abilities on ChromeOS (where there is specialized
hardware) than our abilities on Android (where there is variance in
capabilities based on the OS level and various hardware capabilities) than our
abilities on other platforms that use Chrome/Chromium as the basis for
capabilities (such as ChromeOS).

Even if the WG were to say "Tough, that's Google's problem, you can afford more
lawyers and engineers", every other UA that would have these different profiles
is going to be similarly affected.

This thread has been trying to explain the same issues that have been present
for the past two years. While good to be written down, it doesn't change the
very unfortunate reality of the world, so it would be truly unfortunate to
ignore these issues.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 5 June 2014 16:06:51 UTC