Asylo 0.5.3 Release

[Asylo Users]

We have just released Asylo 0.5.3, containing 166 commits since the last release.

This release introduces the first support for non-C/C++ languages, allowing Java applications to launch and call into enclaves (the enclave itself still must be C/C++). See the new "java" example in the code and the new "Asylo Java Clilent" guide on asylo.dev.

0.5.3 also continued to bring lots of cleanup and technical debt reduction, while making significant progress toward remote attestation APIs.

Changes since 0.5.2 include:

• Updated to the latest Intel SGX SDK to pick up fixes and improvements
• Added bindings for calling into Asylo enclaves from Java applications
• Stability fixes for signal handling in SGX simulation mode
• Performance improvements through more efficient locking mechanisms
• Updated to newer versions of dependencies
• Additional POSIX interface implementations
• Improved documentation and testing
• Maintenance work and bug fixes

Compatibility:

• The SGX SDK update included changes that are not binary compatible with previous releases. When updating to Asylo 0.5.3, ensure you rebuild both your enclave and its loader.
• The non-standard ENCLAVE_STORAGE_SET_KEY ioctl request has been moved to <asylo/secure_storage.h>. The implicit definition by including <sys/ioctl.h> is deprecated and will be removed in a future release. If using Asylo secure storage, ensure that the secure_storage.h header is included where needed.

The release can be found on GitHub at https://github.com/google/asylo/releases/tag/v0.5.3. You can join the discussion on the asylo-users mailing list with feedback and questions for the community.