Enarx (Page 2)

Confidential Computing: logging and debugging

Log entries and other error messages can be very useful, but they can also provide information to other parties.

Enarx's Website

The Enarx project has a new website [https://enarx.dev/]! With the first release [https://blog.enarx.dev/alamo-first-release/] of Enarx, there was a need for a new website focused on documentation to receive developers interested in learning more about the project. The website is divided into two sections: Documentation

Alamo: First Release

It has been 3 years since Mike Bursell and Nathaniel McCallum came together with an idea to build an architecture-neutral framework to run applications within Trusted Execution Environments (TEEs). After going through a set of proofs of concept and underlying engineering stages, the Enarx project came to life. Important milestones

Confidential Computing Fellowship

As the Enarx [https://github.com/enarx/enarx] project is getting ready for its first release, we are focused on enhancing our documentation and building demos. We want to make it easy for potential users to understand Enarx and to see how it works. To help us with the documentation

enarx

Enarx and a New Custodian

The Enarx project has a rich history around openness and collaboration. It was a key project in the foundation of the Confidential Computing Consortium from the Linux Foundation and played an important role in the Bytecode Alliance, the nonprofit behind the WebAssembly standard. The Enarx project was born when Mike