Conclave 1.2 delivers

Conclave 1.2 has been released now, and R3 has been working hard to meet their main goal that is that the enclave doesn’t lose data memory by enhancing its ability to persist data. So meeting the demand on enhancing various areas of Conclave scenarios such are these were addressed:

  • How can an enclave be migrated to another machine?
    A cloud-based Key-Derivation Service, which enables you to deploy your application not tied to any one machine, so you easily migrate enclave data from one VM to another, unlock clusters and high-availability architectures, and enable seamless redeployment of VMs by cloud service providers.

  • How to re-start an enclave from a previous state? The persistent file system gives the enclave the ability to securely store data on the host, and data is still available even after the enclave restarts.

  • How to prevent a malicious actor from state attacks? Key-value store, represented as a standard java.util.Map object. Conclave will securely persist the encrypted map on the host side. Not only is the map still securely available after an enclave restarts, but it is also resilient against attempts by a malicious host to roll it back to a previous state (rollback attacks).

  • How to make it easier for developers to write applications? Out-of-the-box‘Common Host’and ‘Common Client’ to radically simplify the developer journey. This removes the need to develop boilerplate hosting logic by massively reducing the time and complexity of developing the host. Writing your enclave code in Java 11 is possible, and experimental support for Python is available.

In addition, Conclave 1.2 delivers:

  • Enclave lifecycle methods for enclave startup initialization and shutdown cleanup.
  • Further improvements to the Conclave Gradle plugin to reduce the amount of boilerplate code needed.
  • Improved API for checking platform support.
  • Upgraded to For more latest Intel SGX SDK 2.14, which addresses the latest security fixes and other improvements.
  • Host load is no longer required to specify enclave class name as a parameter.

For more information please visit R3’s latest blog posts about Conclave 1.2 :

Get started with a free 30 day trial !