Ryan Hurst

"Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type"

It seems our allowance for GCM in the use of EnvelopedData is the root of the interop issue. I agree the PR is about adding support for this new type.

Rob has published a tsv of a CTL that might be a useful test vector when we do this - https://github.com/robstradling/authroot.stl

Yury, I recall you made an example working in browser later? Am I wrong? If not please describe again what is missing, if I recall correctly we need 3des and...

@YuryStrozhevsky we need to create a Windows compatible PFX in the browser, do you have examole of this? Its hard to understand from your response.

You should still encrypt. You can get 3DES with: https://github.com/PeculiarVentures/webcrypto-liner/blob/master/README.md See the Node example of how to do it. Modern Windows also supports AES p12s now.

The node example produces a file Windows, OSX and Firefox can open. https://github.com/PeculiarVentures/PKI.js/tree/master/examples/NodePKCS12Example For broad compatability with one file you have to use the suites in that sample. Once you...

I have looked into the nRF52840, it provides only acceleration and no key protection or other security isolation concepts. That said it looks like a great platform if you don’t...

Yes, our current thinking is that once all the blocking issues are addressed (assuming that can be done) we will make that switch. Right now some algorithms can't be implemented...

The current known issues are here: https://github.com/PeculiarVentures/webcrypto/issues?q=is%3Aissue+is%3Aopen+label%3A%22blocking+deprecation+of+node-webcrypto-ossl%22 We have done benchmarking and in all cases, if I recall correctly the performance between node-webcrypto-ossl was essentially the same or marginally faster....