2 ms·
Is that really the case? If I'm not mistaken, secure enclaves have a different security model than the use cases you're suggesting: They are so a third party c
by dnautics 7y ago
Is that really the case? If I'm not mistaken, secure enclaves have a different security model than the use cases you're suggesting: They are so a third party can run software on a user's machine without trusting the user. For example, delivering encrypted drm software to a customer that might be trying to crack it.
- jdsully 7y agoIt's so you can run software without trusting the operating system. And by extension that implies the root user as well, but that's not always the use case (it is for DRM). E.g. you might want your credit card processing in an enclave even if it's your own card, simply to hide it from any rootkits or malware you may have installed.
- ptx 7y agoFor the user, there is no real point to such a separation. If the system is full of rootkits and malware, the credit card can be hijacked through for the browser, for example. You don't need to get at the actual credit card processing if you can control all inputs and outputs.