STM32 CryptoLib - Verifyin on Linux machine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-02-13 4:01 AM
Hello everybody,
I'm tryin to make a Nucleo-F401 sign a message and then verify this message on a Linux machine. Currently I am able to inject both private and public key into the STM32F401RE (and, starting from ECDSA keygen and sign example, I checked that it works). However, the public keys given by Python ECDSA and CryptoLib are different. Since I'm using the same curve for both (FIPS 186-3 NIST256P), what can cause this behaviour?
Regards,
Fabio
#cryptographic-library #ecc #cryptography #elliptic-curve #ecdsa #x-cube-cryptolib- Labels:
-
Cryptography
-
STM32F4 Series
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-02-13 5:36 AM
Hi
Angeletti.Fabio
,Try to make sure that you use the same private key forPythonECDSA and CryptoLib
Verify that the CRC module is enabled on your case
-Nesrine-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-02-13 6:59 AM
I verified both, it is exactly what I found scavenging on google. Already tried with both endians. Any other suggestion?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2017-03-01 7:16 AM
I'm still tryin to solve the issue. The Private Key seems to be the same, anyone has some working source code to share? It's really strange that it is not working as expected
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2018-03-22 8:30 PM
Hi Fabio, I am doing the same thing. Hope we can nail it down together. Pls leave me a contact if you agree to make it a team work. Thanks.
