Hi, thanks for your interest in Asylo :)
Asylo provides an SGX simulation mode to test your enclave code on non-SGX enabled machines, and a remote backend that allows you to treat a remote machine as your secure execution context.
Neither of these intrinsically encrypt your memory in use, so to get that security property, you’d need to use an SGX-enabled machine with the sgx_hw backend.
Asylo does not have an AMD SEV backend. SEV and SGX are significantly different technologies, but the backend abstraction could in general work for SEV.
Cheers,
Dionna (Asylo team)
--
Visit asylo.dev for the latest information.
---
You received this message because you are subscribed to the Google Groups "Asylo Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to asylo-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/asylo-users/989d39e3-d0c0-4f66-8090-9ac36e944ca4n%40googlegroups.com.
Bao, I do apologize, but I cannot comment publicly about our roadmap.
To ΓΙΩΡΓΟΣ, it seems you’re asking if attestation works without real SGX hardware? If so, then yes the attestation code works in sgx-sim mode and is suitable for testing purposes. Please keep in mind the attestation is rooted in hard-coded software keys (see https://github.com/intel/linux-sgx/blob/master/sdk/simulation/tinst/deriv.cpp) and could be forged by anyone with the key.
Cheers,
Dionna (Asylo Team)
To view this discussion on the web visit https://groups.google.com/d/msgid/asylo-users/97573f80-d3ea-4fa7-80e8-c82b2ce1b5fen%40googlegroups.com.