W3C home > Mailing lists > Public > public-webcrypto-comments@w3.org > November 2014

Re: Plans on PKI

From: Tien Duc Le <tle@haw-landshut.de>
Date: Fri, 14 Nov 2014 20:17:32 +0100
Cc: "public-webcrypto-comments@w3.org" <public-webcrypto-comments@w3.org>
Message-Id: <FA65A891-2E21-4325-82EC-34042B362150@haw-landshut.de>
To: Richard Barnes <rlb@ipv.sx>
Where did I say that it’s important for the browser to provide the functions? I already looked at PKI.js (further PKCS#7 functionality will be implemented some day in the future) and also Forge (implementing WebCrypto in the near future) and I just wanted to ask for a statement from the WebCrypto side to sum that up in my chapter about Web Cryptography API. Thanks for your explanation.

> Am 14.11.2014 um 20:07 schrieb Richard Barnes <rlb@ipv.sx>:
> 
> Why do you think it's important for the *browser* to perform those functions, instead of a JS library.  The performance, policy, and isolation benefits of WebCrypto don't really apply to the PKI functions you mention, and there are good JS libraries.   In addition to PKI.js, I've also worked with forge.js.
> 
> https://github.com/digitalbazaar/forge <https://github.com/digitalbazaar/forge> 
> 
> On Fri, Nov 14, 2014 at 3:19 AM, Tien Duc Le <tle@haw-landshut.de <mailto:tle@haw-landshut.de>> wrote:
> Hi,
> 
> I am currently working on my bachelorthesis in computer science and I would like to ask, if there are any plans (beside PKI.js) on PKI functions (e.g. PKCS#7, PKCS#12) for the Web Cryptography API?
> 


Received on Friday, 14 November 2014 19:17:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:29 UTC