Thank you for your reply, they make sense a lot!
> > But Enclave written in C is not taking advantage of rigorous checking of
> > Rust sgx_tstd but instead relies on Intel's tlibc (and Intel does not
> > provide checks on the primitive ocalls? I believe they also do?)
>
> I think there's one
> In short, you cannot use third-party Rust crates which are not in the
> `third_party/crates-sgx` directory.
>
> For your case, if you want to use ndarray, you need to vendor ndarray-sgx
> (https://github.com/mesalock-linux/ndarray-sgx) in the `crates-sgx` directory.
ok i'll try.
Can you
mssun merged pull request #2:
URL: https://github.com/apache/incubator-teaclave-website/pull/2
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
I put this wiki page
(https://github.com/apache/incubator-teaclave-sgx-sdk/wiki/Mitigation-of-Intel-SA-00219-in-Rust-SGX)
to our blog
(https://teaclave.staged.apache.org/blog/2019-12-02-mitigation-of-intel-sa-00219-in-teaclave-sgx-sdk/).
It's more like a blog post than document.
--
You are
In short, you cannot use third-party Rust crates which are not in the
`third_party/crates-sgx` directory.
For your case, if you want to use ndarray, you need to vendor ndarray-sgx
(https://github.com/mesalock-linux/ndarray-sgx) in the `crates-sgx` directory.
--
You are receiving this because
Sorry, it seems that my reply brings you more questions.
> But Enclave written in C is not taking advantage of rigorous checking of Rust
> sgx_tstd but instead relies on Intel's tlibc (and Intel does not provide
> checks on the primitive ocalls? I believe they also do?)
I think there's one
