Page MenuHomePhabricator

Platform: Disallow repeated provisioning on Musca-S1
Closed, ResolvedPublic


The Musca-S1 does not have a real OTP, so its crypto hardware values are saved to MRAM instead. Before, the life-cycle state was only checked on the S1 from the MRAM once
provisioning was already done. This resulted in being able to run provisioning repeatedly. Change this so that the values in the MRAM are used always, so that one needs to wipe the MRAM to repeat the process. Also, update the relevant docs.


Event Timeline

BalintMatyi closed this task as Resolved.Jun 8 2020, 10:48 AM