Open dlongley opened 10 years ago
@dlongley Currently the WebCrypto API is heavily broken in certain areas. The Chromium dev's are working on it, but I'd hold off until M38 to save a lot of hair pulling! There is nothing worst than debugging crypto...
I'd also consider waiting until the Typed array backed forge buffer is implemented, will make life so much more easier when implementing WebCrypto API!
I'd also consider waiting until the Typed array backed forge buffer is implemented, will make life so much more easier when implementing WebCrypto API!
Agreed. Buffer interface and implementation changes are first on the API change/update list for forge.
Would be interesting to see such polifill. Meanwhile, you can check PKIjs as an example for Web Cryptography API usage.
I'm sorry, I didn't understant, does forge implement Web Crypto API for now?
Of course forge does not implement Web Crypto API.
@BaurzhanSakharlev, not yet, but incorporating what is useful from WebCryto is on the road map. See: https://github.com/digitalbazaar/forge/issues/203
Forge does not yet implement the Web Crypto API. It provides many of the same features (and others that Web Crypto does not yet provide), but through a different API. We do plan to also provide these features through the same Web Crypto API so forge can act as a polyfill.
Implement the WebCrypto API so forge can act as a polyfill. This issue may be split up into separate parts to implement the API piecemeal. The WebCrypto API is finally being exposed in Chrome 37 so any work on this would be great.