- From: <bugzilla@jessica.w3.org>
- Date: Sun, 30 Nov 2014 19:25:49 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25619 Harry Halpin <hhalpin@w3.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |hhalpin@w3.org Resolution|--- |FIXED --- Comment #2 from Harry Halpin <hhalpin@w3.org> --- It seems cryptographic provider has been defined adequately in the spec now: "an abstraction for a specific implementation of a set of algorithms. The operating system or library may come with a default provider, and users are frequently allowed to add additional providers, reconfigure the set of enabled algorithms, or otherwise customize how cryptographic services are provided. While it is assumed that most user agents will be interacting with a cryptographic provider that is implemented purely in software, it is not required by this specification. As a result, the capabilities of some implementations may be limited by the capabilities of the underlying hardware, and, depending on how the user has configured the underlying cryptographic library, this may be entirely opaque to the User Agent." -- You are receiving this mail because: You are on the CC list for the bug.
Received on Sunday, 30 November 2014 19:25:50 UTC