cryptographic implementation for STM32F103FZT6

[akshada]

Hello Friends,
I am doing a project around stm32f103 which exchanges data with the server. Right now,we have not provided any security to our data that goes to(or from) microcontroller from(or to) server. I want to know does ST provides any cryptographic stack for this microcontroller. and if not how can i implement the same in the application code and the server.

Thanks in advance.

 

[willis...]

Hello Friends,
I am doing a project around stm32f103 which exchanges data with the server. Right now,we have not provided any security to our data that goes to(or from) microcontroller from(or to) server. I want to know does ST provides any cryptographic stack for this microcontroller. and if not how can i implement the same in the application code and the server.

Thanks in advance.

From the STM32 Technical Release (found at https://www.newark.com/pdfs/techarticles/stmicro/brstm320508.pdf)

STM32 encryption library - AES-ECB 128 encryption for STM32F103x
Optimized crypto library for the STM32 32-bit microcontroller, mainly for data-security needs. The AES-ECB 128-bit
symmetric key algorithm coupled with the STM32 Cortex-M3 provides great performance with strong data protection.
The AES-ECB 128-bit benchmark for the STM32 is available upon request with 16-, 32-, 64- and 128-byte plaintext for
Keil, IAR and Hitex toolchains.

However, this library is not directly downloadable from their website; it requires some extra paperwork. I would contact ST for more information.

Regards,
Willis

 

[akshada]

Thanks for the reply, I have contacted the local ST FAE but they said that there is no cryptographic library available for this particular controller(stm32f103zf). can you suggest some other alternative.

Thanks

 

[sky_123]

There were lots of threads on how to read content from microcontrollers with locked bits recently, and threads on how to implement security for a microcontroller in a battery. You could search for them. Long story short, it won't be secure unless the vendor has specific hardware inside the ic (and even then nothing is impossible). What you need to do is to figure out how secure you want this (i.e. what is the loss in dollars if you don't implement?), and then spend an appropriate amount of time+resources on the problem. Read up on public key cryptos and random number generation mechanisms and hash algorithms. You'll need to know about all three, in detail. Then, you'll know enough to decide what you need to implement (maybe on a different device), and the algorithms you need, and where they should be implemented (specific vendor hardware implementation for example). Then, you can look for appropriate source to interface to it or write your own.