Update CNG algorithm pseudo-handles article#2124
Conversation
Cleaned up redundant information and made the contents more consistent, and attached handle locations for ease of use in non-C++/C applications, from bcrypt.h (version 10.0.26100.0). Added links to IETF / NIST for each specification referenced (authoritative links for ANSI / PKCS could not be found). Some specifications linked may not match up with exactly what is implemented with Windows versions they were shipped with, and the most recent specified was used in place.
|
@microsoft-github-policy-service agree |
|
@ATPStorages : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Thanks for the PR. Since this PR updates so much of the content, I'm going to loop in someone from the product team to make sure everything looks OK to merge. |
|
I'm unsure about what to do about the supposed handle "BCRYPT_RNG_FIPS186_DSA_ALG_HANDLE," as I can't find it the latest SDK. Do you know if it is a preview like the digital signature algorithms (in which, a preview notice would probably be beneficial), or does it not exist at all? |
I'm checking with the team about this handle. Thanks! |
| | **BCRYPT_HMAC_MD2_ALG_HANDLE**<br/>0x00000121 | A handle for the hash-based message authentication code using the MD2 hash algorithm. | [RFC 1319](https://www.ietf.org/rfc/rfc1319.txt), [RFC 2104](https://www.ietf.org/rfc/rfc2104.txt) | | ||
| | **BCRYPT_HMAC_MD4_ALG_HANDLE**<br/>0x00000131 | A handle for the hash-based message authentication code using the MD4 hash algorithm. | [RFC 1320](https://www.ietf.org/rfc/rfc1320.txt), [RFC 2104](https://www.ietf.org/rfc/rfc2104.txt) | | ||
| | **BCRYPT_HMAC_MD5_ALG_HANDLE**<br/>0x00000091 | A handle for the hash-based message authentication code using the MD4 hash algorithm. | [RFC 1321](https://www.ietf.org/rfc/rfc1321.txt), [RFC 2104](https://www.ietf.org/rfc/rfc2104.txt) | | ||
| | Available in **Windows 11, version 23H2** | |
There was a problem hiding this comment.
The handles below are put under a guard in the header for NTDDI_VERSION >= NTDDI_WIN11_ZN, which, from what I could find on the Internet, is "Windows 10.0.25246-25398 / 23H2 / Zinc"
The same sources of information state 24H2 as "NTDDI_WIN11_GE" (with the latest handles in the header file being "NTDDI_WIN11_GA", 24H1)
|
Left a few comments. Happy with the changes at a high level. General comment that links are great, but also can become dead over time. Up to doc folks on best approach. |
alvinashcraft
left a comment
alvinashcraft
left a comment
There was a problem hiding this comment.
This all looks much better to me. Let me know if you have any remaining concerns, @samuel-lee-msft. Otherwise, we can move ahead with the PR. Thanks folks!
|
I'm merging this today, but I'm happy to circle back and make additional updates if anything needs to be tweaked later. Thanks for your contribution @denkisikinoneko |
|
[like] Jessica Krynitsky reacted to your message:
…________________________________
From: Alvin Ashcraft ***@***.***>
Sent: Monday, October 20, 2025 8:22:59 PM
To: MicrosoftDocs/win32 ***@***.***>
Cc: Jessica Krynitsky ***@***.***>; Review requested ***@***.***>
Subject: Re: [MicrosoftDocs/win32] Update CNG algorithm pseudo-handles article (PR #2124)
Merged #2124<#2124> into docs.
—
Reply to this email directly, view it on GitHub<#2124 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ASCZ5QUWKXBSJIA2MHOMKK33YVACHAVCNFSM6AAAAACIKIASFSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMRQGM4DQMZUGI2DSOI>.
You are receiving this because your review was requested.Message ID: ***@***.***>
|
4 participants
Cleaned up redundant information and made the contents more consistent, and attached handle locations for ease of use in non-C++/C applications, from bcrypt.h (version 10.0.26100.0). Added links to IETF / NIST for each specification referenced (authoritative links for ANSI / PKCS could not be found). Some specifications linked may not match up with exactly what is implemented with Windows versions they were shipped with, and the most recent specified was used in place.