Please support web standard crypto.subtle

[MichaelJCole]

Node.js developed it's own crypto API before the WebCrypto API.

Since then, browsers and the web have standardized implementations around the WebCrypto API standard.

This bug is about Node.js missing support for the WebCrypto standard API and reopens #2833 (from 2015).

Asking 3rd party libraries to implement the WebCrypto standard is not responsible from a security standpoint for a variety of reasons from implementation expertise to malware. It is not responsible to put this onto API end users (developers).

Additionally, a variety of implementation differences (like this one) make compatible implementations buggy and error-prone.

Back in 2015, there were arguments for not supporting the WebCrypto standard in Node 0.12.

Today, committing to not supporting the WebCrypto standard is committing to a lack of responsibility for Nodejs as a secure and standards based platform on the web.

[bnoordhuis]

Largely a duplicate of #19826 from earlier this year. The answer is still 'no'.

Places where gaps in the existing crypto API make emulating WebCrypto hard can be taken into consideration. Asking for WebCrypto to be added to core verbatim? Not on the table.

[ryanmurakami]

Locking the conversation. I don't see this conversation becoming productive.