Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
What would you propose to create unique DCT's that contains unique certificates and keys for each other device in production. I know that in SDK 2.4.x there was a way to create DCT's, but how can we do this in 3.5.x or later?
Perhaps you could write a program that downloads the desired information from the internet, probably a private server, and write the information to the DCT using wiced_dct_write. The usage is demonstrated in snip.dct_read_write and the DCT information is outlined in WICED/platform/include/platform_dct.h.
Downloading the certificates from a server won't be an option for us because that'll be an security flaw. We want to put certificates while programming the devices.
We'll probably go with the second option. I believe to do this, we need to generate specific DCT files for each device. (Another option would be generate different application elfs for every device but that would take a lot of time). In the WICED directory, there's a file called "generated_security_dct.h". I believe with using this kind file and a script there could be a way to generate device specific DCT files in SDK 3.x.x. Would that be easy? What would you propose to do? Where can we start for doing this?
the best option for you is to store this iinformation in the user DCT, i.e. at the end of the DCT. Then you could at programming time concatenate the DCT with the specific certificate, and then flash it.