Repository navigation
Please port ncrypto from deprecated HMAC_ apis to EVP_MAC apis #59493
Description
Activity
We have to keep in mind that Node.js still has a requirement to support OpenSSL 1.1.1 for the time being. I think we can certainly support the newer APIs but I'm not sure we can completely eliminate the origin
HMAC_apis just yet. It's something I'll investigate tho.Reacted by Tobias NießenReacted by Dimitri John LedkovYeah, that is the common theme - dotnet and python are in the same situation.
I see that KMAC was added with EVPMAC support; thus it is possible there is enough ncrytpo.cc bits to actually implement crypto_hmac.cc with EVPMac
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.this is still desired.
nginx, python, dotnet all moved to support evp mac API in addition to the older HMAC API to gain support for openssl 4.0.
- added a commit that references this issue
on Jun 16, 2026 - added a commit that references this issue
on Jun 19, 2026 - added a commit that references this issue
on Jun 20, 2026 - added a commit that references this issue
on Jun 25, 2026 - added a commit that references this issue
on Jul 30, 2026
deps/ncrypto/ncrypto.cc currently uses HMAC_ apis.
These APIs are widely available in multiple openssl-like implementations.
In OpenSSL however they are deprecated and by-pass provider framework, as well as potentially hardware acceleration.
These APIs will be removed, please consider switching to EVP_MAC APIs instead.