I'm starting a next major version of rust-sgx-sdk which could be merged into
Rust's std, along with several compiler changes, new features, and lint tools.
One of Pre-RFCs is
[here](https://internals.rust-lang.org/t/pre-rfc-always-panic-feature-and-lint-rule/9786).
Would you switch back to rust
The code you referred to is exactly Fortanix's code. The JoinHandle is
implemented using untrusted Mutex. I don't think their implementation could
provide any trustworthiness. They bring too much uncertainty to the SGX
environment. Personally, I strongly disagree with their implementation becaus
The current code of SGX_QUEUE (with rust-sgx-sdk) is not depending on untrusted
Mutex -- it relies on sgx_spin to provide atomicity which keeps everything
inside.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://gith
Yeah I 100% trust you :)
Correct me if I'm wrong:
[`SGX_QUEUE`](https://github.com/dmlc/tvm/blob/7cd986db0e67583bc347ed208c25be4c0d0c32a0/rust/runtime/src/threading.rs#L198)
relies on the implementation of `Mutex` inside SGX. In Fortanix's solution,
it's relies on
[`WaitQueue`](https://github.
No offense.
The difference between rust-sgx-sdk and Fortanix EDP roots from basic
assumptions of security. Fortanix EDP is not designed for security, so it has
assumptions of trusting the OS. For example, the atomicity of EDP's SGX
`RwLock` is **untrusted**. Technically, Fortanix EDP maintains
