Secure boot will not avoid load firmware on a different hardware
Posted: Wed Sep 11, 2019 1:21 pm
The first test I have done, it is to dump the memory from address 0 of a module
I was expecting that the firmware won't boot. I was wrong! The board boot without problem and activate secure boot on the new module.
So if someone will clone my hardware, he can just dump the memory and use it on a cloned hardware.
My question is: how can I achieve the firmware that will boot only on my hardware? If someone clone
I was expecting that the firmware won't boot. I was wrong! The board boot without problem and activate secure boot on the new module.
So if someone will clone my hardware, he can just dump the memory and use it on a cloned hardware.
My question is: how can I achieve the firmware that will boot only on my hardware? If someone clone