-
Updated
Nov 5, 2020 - C
sgx
Here are 110 public repositories matching this topic...
-
Updated
Jun 14, 2020 - C
-
Updated
Nov 6, 2020 - Rust
-
Updated
Sep 3, 2020 - Python
-
Updated
Oct 13, 2020 - C
-
Updated
Jan 14, 2018 - C
-
Updated
Feb 19, 2020 - C++
-
Updated
Nov 7, 2020 - Go
-
Updated
Sep 6, 2020 - Rust
-
Updated
Mar 10, 2020 - Rust
-
Updated
Jul 31, 2020 - C
-
Updated
Aug 27, 2020 - C
-
Updated
Sep 12, 2020 - JavaScript
-
Updated
Nov 6, 2020 - Rust
-
Updated
Nov 6, 2020 - BitBake
-
Updated
Oct 22, 2019 - Dockerfile
-
Updated
Nov 6, 2020 - Shell
-
Updated
Mar 7, 2019 - C
At the moment we do not have support for the Clippy linter in the Veracruz Makefile. Some of Clippy's lint groups would be useful to check on the Veracruz codebase, especially those related to correctness, performance, and idiomatic Rust code style. In the past, I quickly experimented with Clippy on Veracruz but found that lint warnings in our code wer
-
Updated
Mar 6, 2017 - C++
-
Updated
Oct 31, 2020 - C
-
Updated
Jan 12, 2017 - Java
Improve this page
Add a description, image, and links to the sgx topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the sgx topic, visit your repo's landing page and select "manage topics."
Description of the feature
It would be nice to be able to forward some environment variables from the untrusted host e.g. by specifying their names in the manifest.
Example use case: providing the application with a ip+port/domain to connect to (which by definition can be manipulated by the untrusted host anyway).
Please note that this is a different feature than `loader.insecure__use_ho