How to inhibit creation of new keys on SE050

[apaolini]

Hi all,

I'm a perfect newbie to SE050 and I'm trying to inhibit the creation of new EC public keys after I finished creating the ones I need; also, I want to ensure that the values of the keys I created is not modified after that point.

Someone suggested that a secure session can be established and that after that the access to the I2C bus is inhibited to unauthenticated users. I wonder if this is true and if the session's being secured "survives" a power cycle, which I think is not true. For what I understand, a secured session cannot be "sniffed" by a third party, but if the machine is rebooted (or perhaps even before), commands can be transmitted to the SE without authentication.

Could someone please clarify this?

Thank you very much

Andrea Paolini

[Kan_Li · Accepted solution]

Hi @apaolini ,

If you refers to the platformSCP session as the secured session, it is possible to mandate it, so that any use has to do authentication after the power cycle. Please refer to simw-top/doc/demos/se05x/se05x_MandatePlatformSCP/Readme.html for more details.

Have a great day,
Kan

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[apaolini]

Thank you very much!