W3C home > Mailing lists > Public > public-webcrypto-comments@w3.org > October 2012

Re: ECDSA support in practice - Rather limited

From: Ryan Sleevi <sleevi@google.com>
Date: Wed, 24 Oct 2012 09:52:38 -0700
Message-ID: <CACvaWvYeKP=e73WzEWjNMiWSmTt8xkQz8vNKgfVb-K2z9M4PTA@mail.gmail.com>
To: Anders Rundgren <anders.rundgren@telia.com>
Cc: "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>
On Wed, Oct 24, 2012 at 1:58 AM, Anders Rundgren
<anders.rundgren@telia.com> wrote:
> NSS: Supports ECDSA but when used in Firefox (the User Agent) it is not except if you add a suitable *external* crypto provider.
> Windows: .NET 4.5 supports ECDSA but not for usage in TLS (WCF).  Seems to be the case even for W8.
> Android: KeyChain in JellyBean (4.1) seems to not support ECDSA although it is hard to say since the KeyChain documentation is virtually non-existent (the source code is the documentation?).
> I guess the RIM patent is still the issue here?
> Anders

This has been discussed previously at

I suggest if you have you contributions to make to the table, Mike
Jones would be appreciative. As it is, all of the platforms you
mention are already covered.

The support in TLS client libraries is orthogonal to the support in
the low-level cryptographic stack, just like it is orthogonal to the
support within certificate validation/verification libraries. While
they share some overlap, statements about an TLS stack cannot be used
to infer or disprove support within the low-level implementation or
within an X.509 stack.
Received on Wednesday, 24 October 2012 16:53:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:12:48 UTC