cancel
Showing results for 
Search instead for 
Did you mean: 

STM32 cryptographic firmware ECDSA

Roger0x0000
Associate

Hi ST,

     What tool generated the following data?Can you send me this tool? thanks.

 

https://www.st.com/en/embedded-software/x-cube-cryptolib.html

STM32 cryptographic firmware library software expansion for STM32Cube.

 

The path of the code is as follows:

.\STM32CubeExpansion_Crypto_V4.2.0\Projects\NUCLEO-G474RE\Applications\ECC\ECDSA_SignVerify\Src\main.c

 

Roger0x0000_1-1721790709207.png

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/digital-signatures
https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation-Program/documents/dss2/ecdsa2vs.pdf
https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation-Program/documents/dss/186-4ecdsatestvectors.zip (SigGen.txt this vector about 10% into file, grep or search for it)

 

If you want to replicate, convert the message into a byte array, run SHA-224, check d

Use your signing code, the private key and the random data to recreate the signing, and then verify

Make a "pretty printer" to output info in this format for your own keys or whatever.

This is really just a validation pattern people can use to assure the algo is implemented and working correctly.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

View solution in original post

5 REPLIES 5
Joe WILLIAMS
ST Employee

Hi Roger0x0000

 

This post has been escalated to the ST Online Support Team for additional assistance.  We'll contact you directly.

 

Kind Regards

Joe

STMicro Support

Looks to be cut from the NIST test vectors. For some of the newer ones they had .PY scripts too.

But you could test and make your own with things like Micro ECC and there are other Windows tools

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program/digital-signatures
https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation-Program/documents/dss2/ecdsa2vs.pdf
https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation-Program/documents/dss/186-4ecdsatestvectors.zip (SigGen.txt this vector about 10% into file, grep or search for it)

 

If you want to replicate, convert the message into a byte array, run SHA-224, check d

Use your signing code, the private key and the random data to recreate the signing, and then verify

Make a "pretty printer" to output info in this format for your own keys or whatever.

This is really just a validation pattern people can use to assure the algo is implemented and working correctly.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

I unpacked some in to arrays and annotated

https://community.st.com/t5/stm32-mcus-security/ecc-signature-failure/m-p/657551

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..

Thank you, currently I am able to calculate these parameters.