RubNoobs/Systemsicherheit
RubNoobs/Systemsicherheit
3
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Assignment 7 sgximpl: refactor README for project needs
All checks were successful
Latex Build / build-latex (Assignment 4 - Protokollsicherheit (Praxis)) (push) Successful in 1m5s
Details
Latex Build / build-latex (Assignment 5 - Software Security - Teil 1) (push) Successful in 1m4s
Details
Latex Build / build-latex (Assignment 6 - Software Security - Teil 2) (push) Successful in 1m1s
Details
Latex Build / build-latex (Assignment 4 - Protokollsicherheit (Praxis)) (pull_request) Successful in 33s
Details
Latex Build / build-latex (Assignment 5 - Software Security - Teil 1) (pull_request) Successful in 8s
Details
Latex Build / build-latex (Assignment 6 - Software Security - Teil 2) (pull_request) Successful in 6s
Details

Browse source
This commit is contained in:
chronal 2024-07-07 23:03:15 +02:00
parent 1e1095baa0
commit ee1b66a24b
Signed by: chronal
GPG key ID: 25400F3DAABF602F
1 changed files with 25 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
7-SGX_Hands-on/README.md
View file

@ -6,6 +6,16 @@ For more informationm, read the [project description](doc/abgabe.pdf).
We recommend viewing the [repository](https://git.pfzetto.de/RubNoobs/Systemsicherheit/src/branch/Assignment-7-sgximpl/7-SGX_Hands-on) we worked on together at. We recommend viewing the [repository](https://git.pfzetto.de/RubNoobs/Systemsicherheit/src/branch/Assignment-7-sgximpl/7-SGX_Hands-on) we worked on together at.
## Requirements
You will need the latest version of OpenSSL.
Execute the following command to automatically meet all requirements.
```bash
$ ./src/setup
```
## Compiling ## Compiling
This project can be compiled for simulation environments or directly on the hardware. This project can be compiled for simulation environments or directly on the hardware.
@ -26,20 +36,26 @@ At project root type the command
$ make $ make
``` ```
This creates the following directory tree: That creates all the necessary objects and binaries to execute.
The executable binary will be `src/signatureproxy`.
``` ## Running
out
├── bin <- here is the executable binary file ## Running story
└── obj <- here are the object files generated by the compiling process
``` To execute an example usage of the project, execute `./src/simulate`.
Note, that this will only work, if you sucessfully compiled the project.
## Manual Usage
### Setup
Go to the `src` directory.
# Usage
## Setup
Initialize the Enclave keypair by executing: Initialize the Enclave keypair by executing:
`./signatureproxy proxysetup -pkey <sealed_proxy_key.bin> > <proxy_public_key.pem>` `./signatureproxy proxysetup -pkey <sealed_proxy_key.bin> > <proxy_public_key.pem>`
## Sign ### Sign
1. Create employee signature using `./signatureproxy employee -firm <firmware.bin> -ekey <employee_privat_key.pem> > <employee_signature.der>` 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>` 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>` 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>`