henrysun007 opened a new issue, #664:
URL: https://github.com/apache/incubator-teaclave/issues/664

   ### Motivation & problem statement
   
   Current rust version is `nightly-2020-10-25`. It is two years behind 
`nightly-2022-10-22` that is supported by [Teaclave SGX 
SDK](https://github.com/apache/incubator-teaclave-sgx-sdk).
   
   The upgrade plan was also asked. #656
   The old toolchain is not supported by macos-12. #662
   
   ### Proposed solution
   
   Use 
[v2.0.0-preview](https://github.com/apache/incubator-teaclave-sgx-sdk/blob/v2.0.0-preview)
 of Teaclave SGX SDK, which supports 
[cargo-std-aware](https://github.com/rust-lang/wg-cargo-std-aware). 
   
   The 2.0 version reimplements SGX Trts, protected file system and other 
modules with rust. Some underling SGX structures are refactored becoming more 
"rust". The version is still under preview.
   
   #### Strength
   
   Refer to 
[README](https://github.com/apache/incubator-teaclave-sgx-sdk/blob/v2.0.0-preview/README.md)
 of Teaclave SGX SDK.
   
   #### Weakness
   
   I encounted some incompatibility issues due to its incompatibility with 
Intel's implementation when I updated another project using the 2.0 version.
   
   ### Describe alternatives you've considered
   
   Use 
[v1.1.5](https://github.com/apache/incubator-teaclave-sgx-sdk/tree/master) of 
Teaclave SGX SDK. Hundreds of third-party rust crates need to be modified.
   
   Please give some advice, thanks!
   
   @volcano0dr @mssun 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@teaclave.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@teaclave.apache.org
For additional commands, e-mail: notifications-h...@teaclave.apache.org

Reply via email to