You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@teaclave.apache.org by digitalinformation <no...@github.com.INVALID> on 2023/08/26 08:50:46 UTC

[apache/incubator-teaclave-sgx-sdk] Can teaclave completely replace the SGX SDK? (Issue #444)

Hello, I have recently been researching blockchain privacy protection based on Trusted Execution Environment (SGX), can teaclava be a complete replacement for SGX SDK, and what are the advantages over SGX SDK? What languages does teaclave support for trusted blockchain-related development? And where should I start learning about teaclave about developing trusted blockchains? Do you have any examples of this? In addition to replacing the SGX SDK, does teaclave have other functions? Thank you

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/444
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>

Re: [apache/incubator-teaclave-sgx-sdk] Can teaclave completely replace the SGX SDK? (Issue #444)

Posted by Fanghao Yang <no...@github.com.INVALID>.
My understanding is that the Teaclave SGX SDK is essentially a port of rust std and SGX SDK wrapper.  If you are writing C++, you might want to use this https://github.com/intel/linux-sgx

The low-level implementation is done by Intel. So it is just a Rust wrapper but you can write Rust and port existing Rust code into the TEE with much less effort. I suggest you write the Makefile, which shows the exact work to make it work with Rust. The Rust code is compiled into a static library. It will be linked with the edge routine codes (auto-generated wrappers for ECALL and OCALL) as a dynamic library and signed by the SGX enclave signer. Then, your untrusted app can call this shared library to work with the TEE.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-teaclave-sgx-sdk/issues/444#issuecomment-1833983660
You are receiving this because you are subscribed to this thread.

Message ID: <ap...@github.com>