#
trustzone
Here are 36 public repositories matching this topic...
A curated list of public TEE resources for learning how to reverse-engineer and achieve trusted code execution on ARM devices
-
Updated
Feb 13, 2022
Nailgun attack on ARM devices.
android
debugging
raspberry-pi
security
arm
attack
proof-of-concept
exploit
fingerprint
vulnerabilities
trustzone
tee
huawei-mate7
-
Updated
May 13, 2021 - C
Open
Add more examples
4
ShaleXIONG
commented
Apr 1, 2022
Requested feature
We want more examples, particularly, in the following areas, (but not restricted):
- I/O related examples. This can give us more insight into whether our implementation of WASI makes sense and works as expected.
- Pipeline examples. This will be similar to the Linux pipeline
command1 | command2 | command3. In the Veracruz content, the first program,prog_1, writes th
Teaclave TrustZone SDK enables safe, functional, and ergonomic development of trustlets.
-
Updated
Apr 20, 2022 - Rust
Reverse-engineering tools and exploits for Samsung's implementation of TrustZone
-
Updated
Dec 16, 2019 - Python
HITCON electric badge for HITCON CMT 2019.
-
Updated
Mar 19, 2020 - C
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
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
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
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
Solution to harden TLS security by storing private keys and delegating operations to the Trused Execution Environment
-
Updated
Dec 14, 2020 - C
Minimal Zig-based app for Armv8-M + TrustZone
-
Updated
Aug 19, 2019 - Zig
BinaryNinja loader for Mobicore trustlets and drivers
-
Updated
Dec 18, 2019 - Python
Development Docker image for the Veracruz privacy-preserving compute project. Veracruz is an adopted project of the Confidential Compute Consortium (CCC).
-
Updated
Apr 20, 2022 - Dockerfile
A Method for Comparative Analysis of Trusted Execution Environments
-
Updated
Aug 29, 2021 - TeX
TZMon is the security framework for mobile game apps using ARM TrustZone.
-
Updated
Feb 18, 2022 - C
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
(OLD VERSION! Please see the new one at https://github.com/raspiduino/a6lte-kvm) Kernel with KVM for SM-A600G (Samsung Galaxy A6) with exynos7870 cpu
android
linux
arm
kernel
linux-kernel
kvm
qemu
samsung
trustzone
samsung-galaxy
samsung-firmwares
exynos7870
armv8a
-
Updated
Nov 7, 2021 - C
git clone --recursive https://github.com/adrianlshaw/arm-tfm-dev.git && cd arm-tfm-dev && sudo make # Docker-based development environment for Trusted Firmware M
-
Updated
Dec 18, 2020 - Shell
A kernel driver to assist fuzzing code running on higher exception levels.
-
Updated
Jan 17, 2020 - C
Este repositório visa agrupar todas as informações sobre o projeto Atualização de Firmware em Sistemas Embarcados de Forma Segura e Confiável.
-
Updated
Jul 20, 2021 - C
Implementation of OpenSSL ENGINE for OpenVPN with key storage secured by ARM TrustZone
-
Updated
Aug 31, 2021 - C
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
Training Material for Microchip Security Solution
-
Updated
Jul 3, 2019
Improve this page
Add a description, image, and links to the trustzone topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the trustzone topic, visit your repo's landing page and select "manage topics."
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.5Error:
**~/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