Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add Node crypto.getHashes() and hash errors to prepare Hash support #790

Merged
merged 1 commit into from
Jun 23, 2023

Conversation

fhanau
Copy link
Collaborator

@fhanau fhanau commented Jun 20, 2023

No description provided.

@fhanau fhanau requested a review from jasnell June 20, 2023 16:50
// expected to change infrequently based of bssl's stability-focused approach.
return ['md4', 'md5', 'sha1', 'sha224', 'sha256', 'sha384', 'sha512', 'md5-sha1', 'RSA-MD5',
'RSA-SHA1', 'RSA-SHA224', 'RSA-SHA256', 'RSA-SHA384', 'RSA-SHA512', 'DSA-SHA',
'DSA-SHA1', 'ecdsa-with-SHA1'];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine. Are these all of the hashes supported by boringssl or just a subset?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this includes all hashes as listed in https://boringssl.googlesource.com/boringssl/+/fips-20210429/crypto/digest_extra/digest_extra.c#77. boringssl also includes a number of additional deprecated hashes but they are not supported by EVP_get_digestbyname and thus won't be useful in a node crypto context.

@fhanau fhanau merged commit 57fbfec into main Jun 23, 2023
@fhanau fhanau deleted the felix/node-crypto-gethashes branch June 23, 2023 18:40
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants