RE: How to compute MD5 checksum?

Amanda Hsieh — Fri, 09 Aug 2024 20:26:21 GMT

Hi,

[quote user="cscase"]What does CONFIG_NORDIC_SECURITY_BACKEND=y do and why do I need it? Is it documented anywhere? [/quote]

To configure the legacy Mbed TLS APIs, set the option CONFIG_NORDIC_SECURITY_BACKEND

[quote user="cscase"]Why am I able to include mbedtls/md5.h? [/quote]

Because you enable MBEDTLS_MD5_C by default in the kconfig.

-Amanda H.

RE: How to compute MD5 checksum?

cscase — Thu, 08 Aug 2024 16:33:38 GMT

I think I was able to get it working. Here's the information I needed, for reference. To use the MD5 functionality in the mbedtls stuff, I needed to:

1) Put this in my prj.conf. I don't know what it does, why it is necessary, or where/if it is documented (??).

CONFIG_NORDIC_SECURITY_BACKEND=y

2) Put this in my kconfig.zephyr, at the top of the file:

config MBEDTLS_MD5_C

bool "In project definition"

default y

3) Put this in my includes in the file where I want to use the MD5 functions. Initially, it shows red squiggles underneath and says the file is not found, but after doing a build suddenly it's ok. I don't know why this is. (??)

#include <mbedtls/md5.h>

I think it is working because I can use the code below, as from the example zip you pointed at, and it doesn't give build errors:

mbedtls_md5_context ctx;

mbedtls_md5_init(&ctx);

So, I guess I'm good. I hate this about Zephyr and the Connect SDK, though: Sometimes there are mysterious config options I need to include to make something work, and apart from just posting on devzone to ask, I don't know how I'm supposed to find this stuff out. What does CONFIG_NORDIC_SECURITY_BACKEND=y do and why do I need it? Is it documented anywhere? Why am I able to include mbedtls/md5.h? What path is that relative to? It's not where my other includes like kernel.h are, so I don't get why that works here.

RE: How to compute MD5 checksum?

Amanda Hsieh — Thu, 08 Aug 2024 15:08:49 GMT

Hi,

Check out my colleague's sample in this post.

Regards,
Amanda H.