3 ms·
I understand the implication here to be "how can you trust your own hardware anyway," and the answer is "of course in theory you can't." Even if you had SGX an
by akersten 6y ago
I understand the implication here to be "how can you trust your own hardware anyway," and the answer is "of course in theory you can't."
Even if you had SGX and wrote your algorithm or whatever to run in it, if your hardware's compromised, the horse has left the stable. Your proprietary algorithm and input that you developed on the compromised hardware are already available to the attacker. So having SGX locally is not going to help.
At the end of the day, SGX is not going to defend a proprietary computation if the input and algorithm are already compromised.
- anonymousDan 6y agoAs I said in a sibling comment, think if it more as a way of reducing your TCB in cloud environments. Instead of trusting the whole cloud software stack, you now just trust your app and the hw, both of which you need to trust anyway.
- _jal 6y agoI'm not trying to make that argument. I'm literally asking you, what do you use for that purpose?