As of August 2020 the site you are on (wiki.newae.com) is deprecated, and content is now at rtfm.newae.com.

Tutorial P1 Using a Custom Trigger

From ChipWhisperer Wiki
Revision as of 12:22, 24 May 2017 by Fheubach (Talk | contribs)

Jump to: navigation, search

This page is in progress

This tutorial will explore the ChipWhisperer Pro's custom trigger and stream features.

Prerequisites

This tutorial can only be completed using the CW1200_ChipWhisperer-Pro. The ChipWhisperer software and its prerequisites should be installed and the CW1200_ChipWhisperer-Pro and hardware should be connected to each other and your computer. If not, this is the page for you: Installing ChipWhisperer. This tutorial is an extension of Tutorial B1 Building a SimpleSerial Project and Tutorial B5 Breaking AES (Straightforward), which should be completed first for better understanding.

Introduction

Unique to the CW1200_ChipWhisperer-Pro's more advanced FPGA, the stream feature allows continuous power measurement data streaming, removing the upper limit (due to a smaller FPGA) of total samples possible. This allows to you to continuously stream data for a time period in which you can manually send data to the target to record the power response. You can later find the subsection of sample points in the streamed power trace that correspond to the encryption of data. You can now use a subsection of 128 sample points to create a custom trigger using the sum of differences (TODO: link to subsequent section). This eliminates the need for the target to have a code that signals the ChipWhisperer when encryption begins. The subset of points for triggering is chosen by you, so anything is possible... We will explore one possibility in this tutorial.

Building the Target Code

We will begin by modifying the simpleserial-aes.c code with a editor of your choice.

  1. Navigate to the ChipWhisperer installation directory and find the simpleserial-aes folder, the folder is in the ...\chipwhisperer\hardware\victims\firmware directory. The beginning of the file path may be different depending on the installation directory.
  2. Copy the simpleserial-aes folder into the same directory and rename it as you see fit. For example: simpleserial-aes-stream.
  3. Now open the simpleserial-aes-stream folder and rename the simpleserial-aes.c file to match the directory name change. For example: simpleserial-aes-stream.c
  4. Open the simpleserial-aes-stream.c file in the text editor of your choice and find this section of the code near the top.
    /**********************************
     * Start user-specific code here. */
    
    uint8_t get_pt(uint8_t* pt)
    {
    	trigger_high();
    	aes_indep_enc(pt); /* encrypting the data block */
    	trigger_low();
    	simpleserial_put('r', 16, pt);
    	return 0x00;
    }
    
    /* End user-specific code here. *
     ********************************/
    
  5. Modify this code by commenting out the trigger_high(); and trigger_low(); to remove the signal produced by the target to tell the ChipWhisperer it is starting the encryption process. Your c code should look like this:
    /**********************************
     * Start user-specific code here. */
    
    uint8_t get_pt(uint8_t* pt)
    {
    	//trigger_high();
    	aes_indep_enc(pt); /* encrypting the data block */
    	//trigger_low();
    	simpleserial_put('r', 16, pt);
    	return 0x00;
    }
    
    /* End user-specific code here. *
     ********************************/
    
  6. Save this code, and then find the makefile file and open it in a text editor of your choice. Find this piece of code near the top:
    # Target file name (without extension). 
    # This is the base name of the compiled .hex file.
    TARGET = simpleserial-aes
    
    # List C source files here.
    # Header files (.h) are automatically pulled in.
    SRC += simpleserial-aes.c 
    

    Change the TARGET = simpleserial-aes line to TARGET = simpleserial-aes-stream and the SRC += simpleserial-aes.c line to SRC += simpleserial-aes-stream.c

  7. Open your command line in the simpleserial-aes-stream directory and run the make command for the correct target. For example: for the XMEGA run make PLATFORM=CW303. This will create a .hex file in the same directory. This step requires avr-gcc to be set-up and added to your system path. If you have not done this go back to Installing ChipWhisperer under the Required Tools dropdown.

Setting up Stream Mode

  1. Next open the ChipWhisperer software. Hopefully you know how to do this by now.
  2. Run the Project > Example Scripts > ChipWhisperer-Lite: AES SimpleSerial on XMEGA script. We will modify some of the settings.
  3. The modifications to the settings will allow us the use stream mode while manually sending a plain text for encryption. We will then look at the stream data and identify where the encryption takes place and what it looks like.

  4. Under the Scope Settings find the ADC Clock section. Here change the Source setting to CLKGEN x1 via DCM. The ADC Sample Rate field should auto-populate to 7.3846 MS/s or a number approximately equal. If the sampling rate is above 10 MS/s the streaming mode will not work as the buffer in the FPGA will overflow.
    ADC Clock.PNG
  5. Under the Scope Settings find the Trigger Setup section. Enable Stream Mode. The Mode field needs to be set to low so the sample capture starts right away because the target does not set the trigger line to high anymore during encryption.
    Trigger Setup 1.PNG
  6. Under the same section change the Total Samples field to 11000000. This will give use a window of approximately 1.5 seconds to send a plain text and capture the power measurements during encryption.
  7. Note: The Timeout (secs) field needs to be set greater than the time it needs to stream the samples and a little additional time to allow for hardware communication. For example: 11 million samples take about 1.5 seconds at the sampling rate of 7.3MS/s so this field should be set to 2 seconds. You can set it higher if needed.
    Trigger Setup 2.PNG

Capturing the Encryption Process

  1. Now open the terminal inside the Chipwhisperer Capture Software: Tools > Terminal and inside the Terminal window press Connect.
    Terminal.PNG
  2. We will now send a plain text to the target for encryption to test everything is working. For example: pAABBCCDDEEFF00112233445566778899. The target should respond with encrypted text.
    Target response.PNG
  3. Repeat the previous step but before you send a plaintext press capture Capture One Button.PNG and then within one second send the plain text to the target for encryption. Hint: It is easier to do when you already have the plain text ready to send in the terminal and all you have to do is press send. The captured wave form should look like the following:
    Stream Capture.PNG
  4. Note: When pressing capture Capture One Button.PNG, the ChipWhisperer automatically sends a plain text to the target. The plain text and response will show up in the terminal window but we are going to ignore this and focus on our manually sent plain text.

    Looking at the wave form capture you can see that towards the end there is a series of power spikes in the sample data.
    Identifying the Encryption.PNG

  5. Zoom into this area and take a closer look at the power measurements. The sample data should look something like this.
    Encryption Process.PNG
    Here the blue box represent the power usage during the communication and transferring of data too and from the target. The left blue box encompasses the power measurements when the target receives the plain text and the right blue box when the target sends back the encrypted text. The green box encompasses the encryption process.
  6. Zoom into the sample points that represent the encryption process. There should be a pattern that repeats ten times, one for each round of the AES-128 encryption.
    Encryption 2.PNG

Creating a Custom Trigger

We are going to use this repeating pattern to allow the CW1200_ChipWhisperer-Pro to identify when the encryption process occurs and use this to trigger our capture process. We can then use these traces to break the AES-128 encryption exactly the same as in Tutorial B5 Breaking AES (Straightforward).
Trigger Choice.PNG
We will choose the highlighted spike and the surrounding area as our trigger as it is a unique feature that is close to the beginning of the encryption process.

  1. Under Scope Settings find the SAD Trigger Module section. Here choose the 128 data point range that will be used as the trigger. Hint: You can type in a number that is close to the desired location and then click and drag the range selection box to the final position. The position numbers will be different from the ones in this tutorial because the numbers depend on when the plain text was manually sent. So just adjust the numbers as needed. Dragging Selection.PNG
  2. When you are satisfied with the position of your trigger points press Set SAD Reference from Current Trace to set the currently selected points to be used for the sum of absolute differences comparison carried out to activate the trigger.

Note: The Sum of Absolute Differences is carried out during the measurement process and when the total sum of absolute differences of all 128 sample points is below the threshold, the trigger is set to high to start the capture of a trace. This was a specific pattern can be chosen to initiate the capture process without any other data from the target. The SAD equation is as follows:

SAD 
= \sum_{i=1}^{128} |x_{ADC,i} - x_{pattern,i}|

  1. Once you have chosen the points that initialize the trigger you can drag the selection box around and take note of the SAD Reference vs. Cursor value and how it changes. Choose a threshold