| Re: [leshan-dev] Handling of public raw keys |
|
Hi Kai,
Thank you for your fast reply and my apologizes for vague questions. It is one question regarding the secure communication and the other one about provisioning key material as part of lwm2m's bootstrapping process
1: establishing a secure communication channel for the lwm2m protocol. We do have a successful bootstrap process which returns the serverPublicKey, publicKey, e.t.c. in the bootstrap config. Hence, I assume my question should have been how does the lwm2m server and bootstrap server share those keys? Is it approved to store
it in a database which both can utilize? Or does both of them magically generate two identical keys? 2: provisioning key material as part of
lwm2m's bootstrapping process Was basically asking for pointers, best practice, or any "de facto" open source library for generating secure, unique private and public keys used in the RPK_SEC mode. Obviously we would like to follow the lwm2m protocol standard in the keys
Best Regards,
Björn From: leshan-dev-bounces@xxxxxxxxxxx <leshan-dev-bounces@xxxxxxxxxxx> on behalf of Kai <sophokles.kh@xxxxxxxxx>
Sent: Friday, October 16, 2015 12:45 PM To: leshan developer discussions Subject: Re: [leshan-dev] Handling of public raw keys Hi Björn, I am not 100% sure if I get your question right. Are you talking about establishing a secure communication channel over which the lwm2m protocol is supposed to be run or are you talking about provisioning key material as part of lwm2m's bootstrapping process? Regards, Björn Eriksson <Bjorn.Eriksson@xxxxxxxxx> schrieb am Fr., 16. Okt. 2015, 10:32:
|