Hi Olaf,
first, sorry if it is not the right place to ask question about implementation, I did not find any mailing list on topics
I am running your implementation with ECC configured and I wonder about ecdsa_priv_key which is statically defined when running tests/dtls-client./server
thus, here to generate the client's Diffie-Hellman public value (Yc) before sending CLIENT KEY EXCHANGE using :
dtls_ecdsa_generate_key(peer->handshake_params.keyx.ecdsa.own_eph_priv,
ephemeral_pub_x, ephemeral_pub_y,
DTLS_EC_KEY_SIZE);
Correct me if my understanding is wrong : is the ecdsa_priv_key to be generated "randomly" (so, it has to be implemented), e.g for testing purpose, it is defined staticaly for the time being ?
Thanks for your help,
Regards
Gilles
Hi Gilles,
My apologies that there is no mailing list yet. There will be one in the future (as tinydtls is currently in the process of being moved to Eclipse, I did not bother to set up infrastructure somewhere else). I will close this ticket but feel free to send questions to my address given in the source code.
Your understanding is correct: dtls-client.c has a static value for ecdsa_priv_key and the corresponding public curve points ecdsa_pub_key_x and ecdsa_pub_key_y for testing purposes only. A real-world client would need to set its own random key here.