EVP_Digest API and endianess #28042
Unanswered
baluduvvuri1
asked this question in
Q&A
EVP_Digest API and endianess
#28042
Replies: 1 comment 2 replies
-
|
No. The EVP digest APIs handle endian issues internally. There is no endianness in the output format. The output is what it is regardless of the processor's endianness. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Does it indicate while running on LE processor, we do not need to do any byte swap of the output while comparing with the expected result? |
Beta Was this translation helpful? Give feedback.
-
|
I suggest you try it and see. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We run known KAT (known answer test ) for SHA using OpenSSL API's, we use the CAVS SHA test vectors ( FIPS 180 ) to do the validation and the vectors input and results are in “big-endian” convention
Currently we run this test on BE processor and results are fine.
In order to run the SHA test on LE processor, do we need to covert the message input and the result/digest to LE before comparing with the SHA API result/digest? (we use EVP_DigestUpdate for SHA digest)
or
does the EVP API output in particular endian format only?
Beta Was this translation helpful? Give feedback.
All reactions