Securely store data, protected by passwords or other policies, Use se051.

[wenchao-zhang]

Securely store data, protected by passwords or other policies, and delete after exceeding the number of retries. How should this be achieved?

[jesssaid]

If you have experience in developing the A1006 chip, please contact me. Thank you very much! v jesssaid

[wenchao-zhang]

If it exceeds, can it be locked? What if someone brute-force retries the chip? My requirement is very simple. I want to protect confidential data with a password. The password can be read or signed. There is a limit on the number of retries.

[Kan_Li]

Hi @wenchao-zhang ,

Yes, lock is possible with the SetLockState APDU command. but for your case, I think you may create an Auth ID as UserID/ECKey/AESKey, which support max attempts , and create the confidential data with policies that only allow the read/write operations within a session authenticated with the created Auth ID as above. 

Hope that makes sense,

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.
-------------------------------------------------------------------------------

[Kan_Li]

Hi @wenchao-zhang ,

I am sorry, but the SE051 could not automatically delete any secure object after exceeding the number of retries. Such function should be implemented on the host side, on application level, the application counts the error in total and decides whether it is time to delete the data.

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.
-------------------------------------------------------------------------------