Keystone – Open-source Secure Hardware Enclave

Re:Keystone – Open-source Secure Hardware Enclave by mediocrejoker on Thursday December 06, 2018 @07:03PM (#18623816)

Can anyone explain a bit more context around where this would fit in a running system? Would it handle cryptographic operations like key generation, signing etc? How does the boot loader compare to other projects like libreboot?

All of the sys calls in the GitHub repo just set flags in something called magic_mem and then call hitf_syscall, for which I can't find a definition.

[ Parent | on HN ]

Re:Keystone – Open-source Secure Hardware Enclave by tptacek on Thursday December 06, 2018 @07:26PM (#18623984)

It's defined in machine/htif.c. HTIF is a RISC-V thing; see slide 12 of:

https://riscv.org/wp-content/uploads/2015/01/riscv-software-...

There's (I think) an analogous design in the Apple SEP; search "mailbox" in:

https://www.blackhat.com/docs/us-16/materials/us-16-Mandt-De...

[ Parent | on HN ]

Re:Keystone – Open-source Secure Hardware Enclave by mediocrejoker on Thursday December 06, 2018 @09:13PM (#18624552)

Thanks, those slides have some great info.

What exactly does it mean to proxy a syscall to the debugging host?

[ Parent | on HN ]

Re:Keystone – Open-source Secure Hardware Enclave by dayeol on Thursday December 06, 2018 @11:17PM (#18625103)

Thanks for your interest! We've just posted these slides: https://keystone-enclave.org/files/keystone-risc-v-summit.pd...

Keystone is in its early stage, and the first version contains somewhat minimal functioning components.

[ Parent | on HN ]