Skip to content

Update nf-wincrypt-cryptverifysignaturea.md #865

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: docs
Choose a base branch
from
Open

Update nf-wincrypt-cryptverifysignaturea.md #865

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions sdk-api-src/content/wincrypt/nf-wincrypt-cryptverifysignaturea.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -254,7 +254,7 @@ The <b>CryptVerifySignature</b> function completes the hash. After this call, no

If you generate a signature by using the .NET Framework APIs and try to verify it by using the <b>CryptVerifySignature</b> function, the function will fail and <a href="/windows/desktop/api/errhandlingapi/nf-errhandlingapi-getlasterror">GetLastError</a> will return <b>NTE_BAD_SIGNATURE</b>. This is due to the different byte orders between the native Win32 API and the .NET Framework API.

The native cryptography API uses little-endian byte order while the .NET Framework API uses big-endian byte order. If you are verifying a signature generated by using a .NET Framework API, you must swap the order of signature bytes before calling the <b>CryptVerifySignature</b> function to verify the signature.
The native cryptography API uses little-endian byte order while the .NET Framework API uses big-endian byte order. If you are verifying a signature generated by using a .NET Framework API, you must completely reverse the order of signature bytes before calling the <b>CryptVerifySignature</b> function to verify the signature.


#### Examples
Expand Down Expand Up @@ -291,4 +291,4 @@ For an example that uses the <b>CryptVerifySignature</b> function, see <a href="



<a href="/windows/desktop/SecCrypto/cryptography-functions">Hash and Digital Signature Functions</a>
<a href="/windows/desktop/SecCrypto/cryptography-functions">Hash and Digital Signature Functions</a>