This appears to be the meat of it:
https://github.com/keystone-enclave/riscv-pk
with apps:
https://github.com/keystone-enclave/keystone-demo
... there's not much there.
(For the same application, Apple uses L4).
https://github.com/keystone-enclave/riscv-pk
with apps:
https://github.com/keystone-enclave/keystone-demo
... there's not much there.
(For the same application, Apple uses L4).
What's missing?
More:
Workshop on Building Open Source Secure Enclave, with little information about what was presented [1]. The Google slides are superficially interesting: https://keystone-enclave.org/workshop-website-2018/slides/Sc...
Documentation: http://docs.keystone-enclave.org/en/latest/Getting-Started/i...
Mailing list: https://groups.google.com/forum/#!forum/keystone-enclave
Compare to the object/capability schemes in modern L4s.
Well, I don't know what they're doing applications-wise, but there's a seL4 port for RISC-V. Nothing seems to really be stopping anyone from putting enclave applications on seL4 in a RISC-V processor.