nRF9160 https_client sample Mbed TLS/TF-M broken in v2.4.0

[knutgf]

Hi,

In nRF Connect SDK v2.4.0, the nRF9160 https_client sample does not work when compiling with -DOVERLAY_CONFIG=overlay-tfm_mbedtls.conf. The socket connect will give the error -22 or -EINVAL. I have bisected the nRF Connect SDK git history between v2.3.0 and v2.4.0 and found the offending commit to be 6e303d8ccd4bae12a63f163dc339a5563cd9b3e1: https://github.com/nrfconnect/sdk-nrf/commit/6e303d8ccd4bae12a63f163dc339a5563cd9b3e1. The commits before are fine.

My own project that also uses Mbed TLS also stopped working in the same manner.

Regards,

Knut

[knutgf]

For the https_client sample, the solution seems to be to add this to the config:

CONFIG_MBEDTLS_RSA_C=y

[knutgf]

However, with my own code that builds on the aws_client sample, using RSA 2048. I get this error: <err> net_sock_tls: TLS handshake error: -4380. The error seems to be MBEDTLS_ERR_RSA_VERIFY_FAILED.

[Sigurd Hellesvik]

Hi,

I will look into this and return with an answer early next week.

Regards,
Sigurd Hellesvik

[Sigurd Hellesvik]

I was able to reproduce this issue.

I have reported the issue to our developers.
I will let you know when I know more about this

Thank you for the report!

[jonny_v]

I can add an update to this case on behalf of the original poster. We have updated to SDK 2.4.1 and this solved the issue. (option `CONFIG_MBEDTLS_RSA_C=y` is required)