Support webcrypto hash algorithm arguments in node.js crypto hash apis

[jasnell]

What is the problem this feature will solve?

In Node.js, we would do crypto.createHash('sha256') ... in web crypto we can do either crypto.subtle.digest('sha256', ...) or crypto.subtle.digest({ name: 'sha256' }, ...) (string or object). For consistency, it would be helpful to be able to support the webcrypto style arguments in the Node.js APIs also..

What is the feature you are proposing to solve the problem?

const { createHash } = require('node:crypto');

const algorithm = { name: 'sha256' };

// Support the same argument types in createHash/createHmac that are supported in web crypto..

const hash = createHash(algorithm);
// ...

What alternatives have you considered?

No response

[panva]

This would require to run the normalize algorithm¹² name routine in a lot of places if meant to be done consistently across all APIs - this would appear in publicEncrypt, privateDecrypt, digest, hmac, sign, verify, all kdfs, and all other functions that do not even have a webcrypto counterpart but work with digest names.

I don't think we should cater to making node:crypto and SubtleCrypto more like one another, I don't see the payoff for the risk involved.

Footnotes

1. https://github.com/nodejs/node/blob/804d41f9c73c03e670d8e788d14a2237c8c2a057/lib/internal/crypto/util.js#L320-L396 ↩

2. https://w3c.github.io/webcrypto/#algorithm-normalization-normalize-an-algorithm ↩

[github-actions]

There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Mark issue so that it is never considered stale label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.