• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 39 subscribers
  • Views 115 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

LAUNCHCC3220MODASF: Certificate Creation Device Specific

LAUNCHCC3220MODASF: CC3220 created certificate attributes

Roman Jordan
Expert 2051 points

Part Number: LAUNCHCC3220MODASF

Tool/software:

Hello Ti experts,

I created a certificate file /cert/iot/cert.d and the associated key file /cert/iot/csr.de as described in SWRU455M section 17.1.1.4 which uses the NWP commands.
I could not find any settings or parameters that set the position and security attributes of the files to be created.

As shown in the picture below both files are stored with the security attribute set.


1. Which cryptographic method is used to store the public certificate and the corresponding private key?

2. Why is the certificate file, which according to my analysis contains no secrets and is also sent when the TLS network is set up, encrypted at all? Doesn't it make it easier to crack the encryption if you have the data in unencrypted and encrypted form?

Best regards,
Roman

  • 0
    TI__Guru 64475 points

    Hi,

    AES-128-CTR is the selected encryption method. Keys are inherently generated by the device using a True Random Number Generator (TRNG) hardware engine. This means that the key is rotating and random so each file would get encrypted by a different key that is not exposed outside the device.

    It is not needed to have the public certificate encrypted of course since it is sent unencrypted anyway, just the sensitive information like the key.

    But, having it secured would not compromise the other secured file.

    Shlomi