EGETKEY, sgx uses some information to export the secret key, there are several problems

Intel® Software Guard Extensions (Intel® SGX)

Discussion board focused on hardware-based isolation and memory encryption to provide extended code protection in solutions.

EGETKEY, sgx uses some information to export the secret key, there are several problems

480 Views

1. What does the owner Epoch and CPUSVN in the table mean? If they are machine-specific, how does SGX ensure that the same Enclave uses the same seal key on different machines?
2. Should KEYREQUEST be kept secret? If the attacker gets KEYREQUEST, how does SGX ensure that the seal key is not exposed? Is SGX secure by hiding key export functions in hardware?

52 KB

Link Copied

0 Replies

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.