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

Algorithm support - "Native" versus "Polyfilled"

From: Anders Rundgren <anders.rundgren@telia.com>
Date: Tue, 04 Dec 2012 07:55:02 +0100
Message-ID: <50BD9E46.5070405@telia.com>
To: "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>
The Web Crypto API doesn't rely on a provider concept like most other cryptographic APIs do.

A provider only supports a specific set of algorithms and it is usually impossible to expand the set without exporting the key material in clear.

Let's say that you want to do a ECDH operation with a specific KDF and the provider doesn't support the KDF you want to use.  AFAICT you are stuck unless the provider also supports "raw" ECDH which allows polyfilling of the missing KDF.

I don't quite understand how the Web Crypto API deals with this issue.

Received on Tuesday, 4 December 2012 07:33:30 UTC

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