The Wayback Machine - https://web.archive.org/web/20220604194331/https://github.com/topics/trustzone
Skip to content
#

trustzone

Star

Here are 38 public repositories matching this topic...

Language: All
Filter by language
All 38 C 23 Rust 4 Python 2 C++ 1 Dockerfile 1 Java 1 Ruby 1 Shell 1 TeX 1 Zig 1
Sort: Best match
Sort options
Best match Most stars Fewest stars Most forks Fewest forks Recently updated Least recently updated

apache / incubator-teaclave

Star 579
Open

Error: Failed to new the enclave.

Lio101
Lio101 commented Mar 4, 2022

Hi, I am getting error when running ./run-teaclave-services.sh.

Platform: Azure CC VM
OS: Ubuntu 18.04
Docker Image used: teaclave-build-ubuntu-1804-sgx-dcap-1.11:0.1.5

Error:
**~/incubator-teaclave/docker$ ./run-teaclave-services.sh
/dev/isgx device detected.
/var/run/aesmd/aesm.socket socket detected.
Error: No such volume: aesmd-socket
COMMAND: docker-compose -f docker-compose

Read more
help wanted good first issue

veracruz-project / veracruz

Star 133
Open

Add compile-time assertions to check the relative bit width of integer types

dominic-mulligan-arm
dominic-mulligan-arm commented Jan 5, 2021

Various bits of the Veracruz codebase are quite opinionated about the relative sizes of various Rust types, e.g. conversions between usize and u64 are quite common. Technically speaking, these conversions can fail at runtime due to usize not being a fixed-width type in Rust, and these conversions mark one of the few places we still have calls to expect() and unwrap() in the runtime's co

Read more
enhancement good first issue trusted-veracruz-runtime build-process
Find more good first issues

hex-five / multizone-sdk

Star 55

MultiZone® Security TEE is the quick and safe way to add security and separation to any RISC-V processors. The RISC-V standard ISA doesn't define TrustZone-like primitives to provide hardware separation. To shield critical functionality from untrusted third-party components, MultiZone provides hardware-enforced, software-defined separation of multiple equally secure worlds. Unlike antiquated hypervisor-like solutions, MultiZone is self-contained, presents an extremely small attack surface, and it is policy driven, meaning that no coding is required – and in fact even allowed. MultiZone works with any 32-bit or 64-bit RISC-V processors with standard Physical Memory Protection unit (PMP) and “U” mode.

security fpga firmware hypervisor container freertos xilinx microkernel secure-boot risc-v trustzone tee arty trusted-computing sifive multizone trusted-execution-environment secure-element root-of-trust polarfire-soc
  • Updated Feb 24, 2022
  • C

Samsung / mTower

Star 34

mTower is Trusted Execution Environment specially designed to be used on MicroController Units (MCUs) supporting ARM TrustZone technology (e.g., Cortex-M23/33/35p). mTower operates well under restrictions typical for such environment – small RAM and ROM sizes, relatively low performance, absence of rich OSes providing variety of services available on PCs or in enterprise environments. mTower is intended for usage in IoT, embedded devices, Smart Home applications, distributed heterogeneous networks and other environments where secure processing of sensitive data is necessary.

iot microcontroller smarthome makefile gcc secure freertos bootloader trustzone nuvoton trusted-execution-environment cortex-m23 numaker-pfm-m2351 m2351
  • Updated Feb 5, 2022
  • C

hex-five / multizone-iot-sdk

Star 10

MultiZone® Trusted Firmware is the quick and safe way to build secure IoT applications with any RISC-V processor. It provides secure access to commercial and private IoT clouds, real-time monitoring, secure boot, and remote firmware updates. The built-in Trusted Execution Environment provides hardware-enforced separation to shield the execution of trusted applications from untrusted 3rd party libraries.

tls mqtt iot firmware iot-platform freertos xilinx lwip tcp-ip secure-boot mbedtls risc-v firmware-updates trustzone tee arty trusted-computing multizone trusted-execution-environment firmware-security
  • Updated Feb 1, 2022
  • C

hex-five / multizone-sdk-arm

Star 9

MultiZone® Security TEE for Arm® Cortex®-M is the quick and safe way to add security and separation to any Cortex-M based device. MultiZone® software can retrofit existing designs. If you don’t have TrustZone®, or if you require finer granularity than one secure world, you can take advantage of high security separation without the need for hardware and software redesign, eliminating the complexity associated with managing a hybrid hardware/software security scheme.

security cortex-m firmware psa armv7 secure-boot trustzone tpm-firmware trusted-computing separation-kernel secure-operating-system hex-five multizone-security multizone trusted-execution-environment secure-element root-of-trust secure-bootloader trustzone-kernel
  • Updated Jan 25, 2022
  • C

hex-five / multizone-sdk-pfsc

Star 2

MultiZone® Security TEE is the quick and safe way to add security and separation to any RISC-V processors. The RISC-V standard ISA doesn't define TrustZone-like primitives to provide hardware separation. To shield critical functionality from untrusted third-party components, MultiZone provides hardware-enforced, software-defined separation of multiple equally secure worlds. Unlike antiquated hypervisor-like solutions, MultiZone is self-contained, presents an extremely small attack surface, and it is policy driven, meaning that no coding is required – and in fact even allowed. MultiZone works with any 32-bit or 64-bit RISC-V processors with standard Physical Memory Protection unit (PMP) and “U” mode.

security fpga firmware container microkernel secure-boot risc-v trustzone tee safety-critical trusted-execution-environment root-of-trust microchip-polarfire-soc
  • Updated Feb 6, 2022
  • C

hex-five / multizone-sdk-andes

Star 1

MultiZone® Security TEE for Andes N22/AE250 is the quick and safe way to add security and separation to any RISC-V processors. The RISC-V standard ISA doesn't define TrustZone-like primitives to provide hardware separation. To shield critical functionality from untrusted third-party components, MultiZone provides hardware-enforced, software-defined separation of multiple equally secure worlds. Unlike antiquated hypervisor-like solutions, MultiZone is self-contained, presents an extremely small attack surface, and it is policy driven, meaning that no coding is required – and in fact even allowed. MultiZone works with any 32-bit or 64-bit RISC-V processors with standard Physical Memory Protection unit (PMP) and “U” mode.

hypervisor container freertos microkernel secure-boot risc-v trustzone tee andes trusted-computing trusted-execution-environment secure-element root-of-trust trusted-firmware
  • Updated Jan 25, 2022
  • C

Improve this page

Add a description, image, and links to the trustzone topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the trustzone topic, visit your repo's landing page and select "manage topics."

Learn more