#sgx-enclave #intel-sgx #enclave #sgx #sgxs #api-bindings #isgx


Platform-specific loaders for SGX enclaves. The following loaders are supported: * SGX device (Linux) * Enclave API (Windows) * libsgx_enclave_common (Linux & Windows)

10 releases

0.4.0 Apr 16, 2024
0.3.3 Jul 29, 2022
0.3.2 Dec 3, 2021
0.3.1 Dec 18, 2020
0.1.0-rc1 Nov 19, 2018

#216 in Hardware support

Download history 214/week @ 2024-01-22 164/week @ 2024-01-29 187/week @ 2024-02-05 275/week @ 2024-02-12 293/week @ 2024-02-19 327/week @ 2024-02-26 271/week @ 2024-03-04 238/week @ 2024-03-11 269/week @ 2024-03-18 233/week @ 2024-03-25 253/week @ 2024-04-01 210/week @ 2024-04-08 388/week @ 2024-04-15 337/week @ 2024-04-22 286/week @ 2024-04-29 242/week @ 2024-05-06

1,270 downloads per month
Used in 6 crates

MPL-2.0 license

3.5K SLoC

Fortanix Rust Enclave Development Platform

Runtime Encryption Slack Build Status

The Fortanix Rust EDP is the preferred way to write Intel SGX enclaves from scratch.

Get started now.

# Install EDP components
rustup target add x86_64-fortanix-unknown-sgx --toolchain nightly
cargo install fortanix-sgx-tools sgxs-tools
echo >> ~/.cargo/config -e '[target.x86_64-fortanix-unknown-sgx]\nrunner = "ftxsgx-runner-cargo"'

# Check your SGX setup

# Run your enclave!
cargo new --bin hello-world
cd hello-world
cargo run --target x86_64-fortanix-unknown-sgx


Looking for the in-enclave source code? Check out the rust-lang/rust repository.

Note for maintenance

About creating release and publishing to crates.io

The Publish Crates workflow can be triggered or by creating new Release: please ensure the tag name used for the new release following format: ${crate name}_v{version number} , although in this workflow only ${crate name} is used, but {version number} is still required for keeping a good tag name.


We gratefully accept contributions from the community. By participating in this community, you agree to abide by Code of Conduct.

Here are some ways to contribute:

  1. Participate in the #rust-sgx channel of the Runtime Encryption community on Slack.
  2. File bug reports.
  3. Help design new features.
  4. Contribute code via pull requests.

All contributions are covered under the Developer's Certificate of Origin (DCO).

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.


This project is primarily distributed under the terms of the Mozilla Public License (MPL) 2.0, see LICENSE for details.


~75K SLoC