Hello Clemence,

Unfortunately, it's very hard to tell why a TLS client and a TLS
server have a communication problem - TLS is a complex protocol, and
there can be dozens if not hundreds ways it can go wrong. And that's
not counting pure network issues, which can be dozens too.

As part of my work on
https://github.com/zephyrproject-rtos/zephyr/pull/5985 , I made
TLS/mbedTLS samples which work as expected and transfer megabytes of
data from a real-world server (which is hopefully enough to say "it
kinda works", though larger amount and coverage of testing is
definitely required).

The only scalable way to approach issues like you report is to take
known working reference sample(s), then step by step compare it with
your code, to see what you do differently.


Hope this helps.


On Mon, 7 May 2018 14:35:17 +0200
"clemence" <c.njamfa@...> wrote:

Hi,

I am currently trying to integrate mbedtls to open a socket between a
bord NXP FRDM-K64F (client) and a server.

But the function "mbedtls_ssl_handshake" does not work.

The client send "client-hello".

The server receive "client-hello" and send : "server hello" + server
certification. But after 5s, the server send a message to close the
connection.

Why the server send the message to close the connection and what I
need to change in my client to fix it?


Thanks


Clemence

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog