RubNoobs/Systemsicherheit
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Systemsicherheit/7-SGX_Hands-on
History
Sascha Tommasone c9b6e749a7 [Assignment-7] update Makefile and simulate.sh
2024-07-08 11:19:48 +02:00
..
doc Assignment 7: abgabe neue formulierung 2024-07-07 22:13:20 +02:00
employee_keys [Assignment-7] add keys of Bob and Oskar 2024-07-08 11:19:48 +02:00
src [Assignment-7] update Makefile and simulate.sh 2024-07-08 11:19:48 +02:00
.gitkeep [Assignment-7] Flake + App base 2024-07-08 11:19:48 +02:00
flake.lock [Assignment-7] Flake + App base 2024-07-08 11:19:48 +02:00
flake.nix [Assignment-7] update flake and add missing enclave files 2024-07-08 11:19:48 +02:00
README.md [Assignment-7] app restructure and cleanup 2024-07-08 11:19:48 +02:00

README.md

Usage

Setup

Initialize the Enclave keypair by executing: ./signatureproxy proxysetup -pkey <sealed_proxy_key.bin> > <proxy_public_key.pem>

Sign

  1. Create employee signature using ./signatureproxy employee -firm <firmware.bin> -ekey <employee_privat_key.pem> > <employee_signature.der> This step can also be done using OpenSSL: openssl dgst -sha256 -sign <employee_private_key.pem> -out <employee_signature.der> -in <firmware.bin>
  2. Use the signature proxy to resign the firmware using ./signatureproxy proxy -pkey <sealed_proxy_key.bin> -epub <employee_public_key.der> -firm <firmware.bin> > <proxy_signature.der> The enclave verifies the employee signature and signs the firmware if the signature is valid.
  3. Verify signature using cat <proxy_signature.der> | ./signatureproxy embedded -firm <firmware.bin> -ppub <proxy_public_key.pem> This step can also be done using OpenSSL: openssl dgst -sha256 -verify <proxy_public_key.pem> -signature <proxy-signature.der> <firmware.bin>