Sorry, you need to enable JavaScript to visit this website.

Details

Release Date: 
Jan 16, 2020

Intel® SGX Data Center Attestation Primitives

INTRODUCTION

Attestation is the process of demonstrating that a software executable has been properly instantiated on a platform. Intel® SGX attestation allows a remote party to gain confidence that the intended software is securely running within an enclave on an Intel® SGX enabled platform.

WHAT’S NEW

  • Updated Provisioning Certificate Caching Server (PCCS) and added PCCS Administration tool to support retrieving platform certificates in offline mode
  • Added non-QvE (Quote Verification Enclave) based quote verification support
  • Updated Quote verification sample project to demonstrate library interface change
  • Added new Platform Certificate Selection Library interface to return CPUSVN configuration information
  • Fixed bugs.

SYSTEM REQUIREMENTS

HARDWARE REQUIREMENTS

  • Intel® Xeon® E Processor based Server
  • Intel® SGX option enabled in BIOS with Flexible Launch Control support

SOFTWARE REQUIREMENTS

Supported Linux* OS distributions:

  • Ubuntu* 16.04 LTS 64-bit Server version
  • Ubuntu* 18.04 LTS 64-bit Server version

Note: It is highly recommended to use the listed Linux* OS distributions. Other distributions have not been tested.

KNOWN ISSUES AND LIMITATIONS

  • Intel® SGX DCAP 1.4 does not include the latest functional and security updates. Intel® SGX DCAP 1.4.1 is targeted to be released in March 2020 and will include additional functional and security updates. Customers should update to the latest version as it becomes available.
  • During the current release we have learned that the DKMS infrastructure uses the driver version as an arbitrary string and not as a numeric value. As a result, installing an old version on top of a new version will work, moreover, when more than one version is installed and a kernel update occurs there is no guarantee that the new version will be used in the new kernel – apparently either of the existing versions may be used To address these issues, the 1.10 driver installer will uninstall a previously installed driver if exists.

Note: The uninstall may fail if the driver is in use by an enclave or the AESM, in this case the user will be notified and will be required to manually uninstall the driver.