This repository holds the insecure example design for an eCTF MISC system.
application_processor
- Code for the application processorproject.mk
- This file defines project specific variables included in the MakefileMakefile
- This makefile is invoked by the eCTF tools when creating a application processorinc
- Directory with c header filessrc
- Directory with c source fileswolfssl
- Location to place wolfssl library for included Crypto Example
deployment
- Code for deployment secret generationMakefile
- This makefile is invoked by the eCTF tools when creating a deployment- You may put other scripts here to invoke from the Makefile
ectf_tools
- Host tools and build tools - DO NOT MODIFY ANYTHING IN THIS DIRECTORYattestation_tool.py
- Runs attestation command on application processorboot_tool.py
- Boots the application processor and sensorslist_tool.py
- Lists what sensors are currently onlinereplace_tool.py
- Replaces a sensor id on the application processorbuild tools
- Tools to build
component
- Code for the componentsproject.mk
- This file defines project specific variables included in the MakefileMakefile
- This makefile is invoked by the eCTF tools when creating a componentinc
- Directory with c header filessrc
- Directory with c source fileswolfssl
- Location to place wolfssl library for included Crypto Example
shell.nix
- Nix configuration file for Nix environmentcustom_nix_pkgs
- Custom derived nix packagesanalog-openocd.nix
- Custom nix package to build Analog Devices fork of OpenOCD
This repository contains two main elements: firmware source code and tooling.
Firmware is built through the included eCTF Tools. These tools invoke the Makefiles in specific ways in the provided Nix environment. Firmware compiling should be executed through these included tools.
Source code and tooling is provided that runs directly on the host. All of these tools are
created in Python. The tools can be easily installed with the use of Poetry. Once inside
of the activated Nix environment, run poetry install
to initialize the Poetry environment.
These tools can be invoked either through poetry run {toolname}
or by activating the poetry environment
with poetry shell
and then running as standard python programs.
The environment is built with a Nix, which should install all packages
necessary for running the design in a reproducible fashion. The environment is automatically
built when an eCTF Build Tool is run. If building analog_openocd.nix
this step may
take some time to complete.
Development can be prototyped by launching into the Nix environment through nix-shell
.
Host Tools for the 2024 competition do not need to be modified by teams at any point. Your design should work with the standardized interface between host and MISC system. The host tools will pass any required arguments to the MISC system and receive all relevant output.
When creating a deployment, the Makefile within the deployment
folder of the design
repo will be executed. This is the only stage in which information can be shared between
separate portions of the build (e.g. components and application processors). A clean
target should be implemented in this Makefile to allow for elimination of all generated secrets.
When building the application processor and components, the Makefile
with the
respective directories will be invoked. The eCTF Tools will populate parameters into
a C header file ectf_params.h
within the design directory. Examples of these header
files can be found in the respective main source files for the application processor
and component.
This will run the Makefile
found in the deployment folder using the following inputs:
ectf_build_depl --help
usage: eCTF Build Deployment Tool [-h] -d DESIGN
Build a deployment using Nix
options:
-h, --help show this help message and exit
-d DESIGN, --design DESIGN
Path to the root directory of the included design
Example Utilization
ectf_build_depl -d ../ectf-2024-example
This will run the Makefile
found in the application processor folder using the following inputs:
ectf_build_ap --help
usage: eCTF Build Application Processor Tool [-h] -d DESIGN -on OUTPUT_NAME [-od OUTPUT_DIR] -p P
-b BOOT_MESSAGE
Build an Application Processor using Nix
options:
-h, --help show this help message and exit
-d DESIGN, --design DESIGN
Path to the root directory of the included design
-on OUTPUT_NAME, --output-name OUTPUT_NAME
Output prefix of the built application processor binary Example 'ap' -> a
-od OUTPUT_DIR, --output-dir OUTPUT_DIR
Output name of the directory to store the result: default: .
-p PIN, --pin PIN PIN for built application processor
-t TOKEN, --token TOKEN
Token for built application processor
-c COMPONENT_CNT, --component-cnt COMPONENT_CNT
Number of components to provision Application Processor for
-ids COMPONENT_IDS, --component-ids COMPONENT_IDS
Component IDs to provision the Application Processor for
-b BOOT_MESSAGE, --boot-message BOOT_MESSAGE
Application Processor boot message
Example Utilization
ectf_build_ap -d ../ectf-2024-example -on ap --p 123456 -c 2 -ids "0x11111124, 0x11111125" -b "Test boot message" -t 0123456789abcdef -od build
ectf_build_comp --help
usage: eCTF Build Application Processor Tool [-h] -d DESIGN -on OUTPUT_NAME [-od OUTPUT_DIR] -id COMPONENT_ID -b BOOT_MESSAGE -al
ATTESTATION_LOCATION -ad ATTESTATION_DATE -ac ATTESTATION_CUSTOMER
Build an Application Processor using Nix
options:
-h, --help show this help message and exit
-d DESIGN, --design DESIGN
Path to the root directory of the included design
-on OUTPUT_NAME, --output-name OUTPUT_NAME
Output prefix of the built application processor binary Example 'ap' -> ap.bin, ap.elf, ap.img
-od OUTPUT_DIR, --output-dir OUTPUT_DIR
Output name of the directory to store the result: default: .
-id COMPONENT_ID, --component-id COMPONENT_ID
Component ID for the provisioned component
-b BOOT_MESSAGE, --boot-message BOOT_MESSAGE
Component boot message
-al ATTESTATION_LOCATION, --attestation-location ATTESTATION_LOCATION
Attestation data location field
-ad ATTESTATION_DATE, --attestation-date ATTESTATION_DATE
Attestation data date field
-ac ATTESTATION_CUSTOMER, --attestation-customer ATTESTATION_CUSTOMER
Attestation data customer field
Example Utilization
ectf_build_comp -d ../ectf-2024-example -on comp -od build -id 0x11111125 -b "Component boot" -al "McLean" -ad "08/08/08" -ac "Fritz"
Flashing the MAX78000 is done through the eCTF Bootloader. You will need to initially flash the eCTF Bootloader onto the provided hardware.
This can be done easily by dragging and dropping the provided bootloader (for design phase:insecure.bin
) to the DAPLink interface. DAPLink will show up as an external drive when connected to your system. Succesfull installation would make a blue LED flash on the board.
To flash a specific bootloader image on the board (AP or Components), use ectf_update
.
ectf_update [-h] --infile INFILE --port PORT
optional arguments:
-h, --help show this help message and exit
--infile INFILE Path to the input binary
--port PORT Serial port
Example Utilization
ectf_update --infile example_fw/build/firmware.img --port /dev/ttyUSB0
The list tool applies the required list components functionality from the MISC system. This is availble on the
PATH within the Poetry environment as ectf_list
.
ectf_list -h
usage: eCTF List Host Tool [-h] -a APPLICATION_PROCESSOR
List the components connected to the medical device
options:
-h, --help show this help message and exit
-a APPLICATION_PROCESSOR, --application-processor APPLICATION_PROCESSOR
Serial device of the AP
Example Utilization
ectf_list -a /dev/ttyUSB0
The boot tool boots the full system. This is available on the PATH within the Poetry environment as ectf_boot
ectf_boot --help
usage: eCTF Boot Host Tool [-h] -a APPLICATION_PROCESSOR
Boot the medical device
options:
-h, --help show this help message and exit
-a APPLICATION_PROCESSOR, --application-processor APPLICATION_PROCESSOR
Serial device of the AP
Example Utilization
ectf_boot -a /dev/ttyUSB0
The replace tool replaces a provisioned component on the system with a new component.
This is available on the PATH within the Poetry environment as ectf_replace
.
ectf_replace --help
usage: eCTF Replace Host Tool [-h] -a APPLICATION_PROCESSOR -t TOKEN -i COMPONENT_IN -o COMPONENT_OUT
Replace a component on the medical device
options:
-h, --help show this help message and exit
-a APPLICATION_PROCESSOR, --application-processor APPLICATION_PROCESSOR
Serial device of the AP
-t TOKEN, --token TOKEN
Replacement token for the AP
-i COMPONENT_IN, --component-in COMPONENT_IN
Component ID of the new component
-o COMPONENT_OUT, --component-out COMPONENT_OUT
Component ID of the component being replaced
Example Utilization
ectf_replace -a /dev/ttyUSB0 -t 0123456789abcdef -i 0x11111126 -o 0x11111125
The attestation tool returns the confidential attestation data provisioned on a component.
This is available on the PATH within the Poetry environment as ectf_attestation
.
ectf_attestation --help
usage: eCTF Attestation Host Tool [-h] -a APPLICATION_PROCESSOR -p PIN -c COMPONENT
Return the attestation data from a component
options:
-h, --help show this help message and exit
-a APPLICATION_PROCESSOR, --application-processor APPLICATION_PROCESSOR
Serial device of the AP
-p PIN, --pin PIN PIN for the AP
-c COMPONENT, --component COMPONENT
Component ID of the target component
Example Utilization
ectf_attestation -a /dev/ttyUSB0 -p 123456 -c 0x11111124