-
Updated
Mar 25, 2021 - C
sgx
Here are 121 public repositories matching this topic...
-
Updated
Mar 26, 2021 - Rust
-
Updated
Feb 25, 2021 - C
-
Updated
Sep 3, 2020 - Python
-
Updated
Dec 2, 2020 - C
-
Updated
Jan 14, 2018 - C
-
Updated
Feb 19, 2020 - C++
-
Updated
Mar 26, 2021 - C
Since raw queries only return encrypted keys, it's pointless and will break implementations coming from other networks without letting anyone know.
We should remove it from the next version
-
Updated
Sep 6, 2020 - Rust
-
Updated
Mar 27, 2021 - Go
-
Updated
Mar 10, 2020 - Rust
-
Updated
Mar 9, 2021 - C
-
Updated
Jan 5, 2021 - C
-
Updated
Mar 26, 2021 - Go
Describe the bug
The BUILD_INSTRUCTIONS.markdown is hard to follow, especially in light of our recent Docker changes.
To Reproduce
Follow the BUILD_INSTRUCTIONS.markdown file in conjunction with the contents of README.md in veracruz-docker-image.
Expected behaviour
A few points of inconsistency, or things that could be clarified, stand out:
- The Intel IAS service
-
Updated
Mar 27, 2021 - C++
-
Updated
Sep 12, 2020 - JavaScript
-
Updated
Mar 28, 2021 - Rust
-
Updated
Mar 26, 2021 - BitBake
-
Updated
Oct 22, 2019 - Dockerfile
-
Updated
Mar 26, 2021 - Shell
-
Updated
Mar 7, 2019 - C
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