U2F Zero

Overview

U2F Zero is an affordable and physically secure two factor authentication token that implements the U2F protocol.

Hardware

The device uses Silicon Labs' EFM8UB1 microcontroller to provide a USB interface and implement U2F. It uses Atmel's ATECC508A chip for true random number generation, hardware accelerated ECC key generation and signatures, atomic counters, and tamper resistant storage for private keys. EFM8UB1 and ATECC508A interface via a I2C command set.

The device also has an RGB LED for status indication and a button to receive user input.

USB pins are exposed copper zones on the PCB. A 2mm thick PCB is recommended for best fit but 1.6 mm will work as well.

Firmware

Program flow

The program generally follows this execution flow:

Main loop:

• Check if USB is busy and schedule a read if USB is free
• If USB interrupted with a read, pass the newly read message to HID layer

HID layer:

• Read a HID packet passed to it
• Implement HID commands and sequencing as described in the U2F HID layer spec
• If the HID message contains a U2F packet, buffer it or pass complete U2F packet to the U2F layer

U2F layer:

• Read a U2F packet
• Implement authenticate and register commands as described in U2F raw message spec
• Handle any key generation, signatures, and atomic counting through I2C commands with ATECC508A

I2C layer:

• Receives a command and empty buffer for ATECC508A response
• Wake the ATECC508A from suspension
• Send the formatted command with CRC16.
• Receive ATECC508A response and check for errors and verify received CRC16.
• Put ATECC508A device into suspension
• I2C I/O and CRC calculations are interrupt based and done byte by byte.

Code organization

The HID and U2F layers are written to not be device specific and can easily be ported elsewhere.

EFM8UB1 USB driver:

• descriptors.c
• descriptors.h
• callback.c

EFM8UB1 I2C driver:

• Interrupts.c
• i2c.c
• i2c.h

ATECC508A I2C layer:

• atecc508a.c
• atecc508a.h

HID layer:

• u2f_hid.c
• u2f_hid.h

U2F layer:

• u2f.c
• u2f.h
• u2f-atecc.c // device specific implementation

Build a U2F Zero token yourself

What's the point of an open source project if you can't build it yourself?

Hardware

You need the parts listed in this . You should be able to purchase all the surface mount parts from Digikey.

You can order the PCB's from Dirty PCB's using this .

You can check the Kicad schematic and layout in hardware/ for soldering information or follow this .

Firmware

Prerequisites and dependencies

You need to install Simplicity Studio to build the project.

You also need python and the python hidapi module for initial set up of device.

You can install hidapi with pip:

sudo pip install hidapi

You will need openssl installed and openssl libraries for creating and signing an attestation certificate.
If you do not wish to do this, it is not needed.

You will also need a programmer for Silicon Labs C2CK/C2D wire devices.

Opening the project

• Open Simplicity Studio
• Click File -> Import
• General -> Existing Projects into Workspace
• Select root directory and choose the firmware/ directory
• Finish

Setup device

You will need to make two builds. First build is the setup build. It does not implement U2F but rather just has everything to write the configuration for the ATECC508A and lock it. It also has to generate a key used for attestation and signing during U2F registrations. You can ask me to sign your key using the master U2F Zero signing key or you can sign it yourself. Both will work.

First open "app.h" and uncomment "ATECC_SETUP_DEVICE". Now build and program the device.

Now to check the device works, lock it, and get the public key used for attestation.

cd tools/hid_config
./config.py pubkey.hex

The ECC public key X,Y values will be stored in hex in pubkey.hex if setup is successful.

Now to create an attestation certificate from the public key. You have a number of different options. You can give the public key to me to create and sign it (with proof of U2F Zero key ownership), or you can sign it yourself.

To sign it yourself:

# create your own "certificate authority" key signing pair and certificate

# generate EC private key
openssl ecparam -genkey -name prime256v1 -out key.pem

# generate a "signing request"
openssl req -new -key key.pem -out key.pem.csr

# self sign the request
openssl x509 -req -in key.pem.csr -signkey key.pem -out cert.pem

Now to sign the public key received from the device at setup.

pub=$(cat tools/hid_config/pubkey.hex)
cd tools/gencert

# edit signcert.c to add the certificates fields you want

make
./hex2pubkey $pub pubkey.pem

# sign public key and save certificate in DER
./signcert ca/key.pem cert.der

Now we are ready to make the final device build. We will need to copy the DER certificate into the build.

cd tools/

# convert bytes to C string
cat gencert/ca/cert.der | gencert/cbytes.py > pubkey.c.txt

# copy to source code
insert_key/insert.py ../firmware/src/u2f-atecc.c pubkey.c.txt ../firmware/src/u2f-atecc.c

# or you can copy it in manually

Uncomment "ATECC_SETUP_DEVICE" in app.h. Build and program the device.

Programming

You need three jumper cables and a Silicon Labs C2CK/C2D wire capable programmer. Most development boards or this debugger will work.

Connect the C2CK and C2D wires from programmer to the respective C2CK and C2D pins on the board.

Connect ground of programmer cable to sit under the ground leg of the push button or other USB ground.

You should be able to detect the chip from Simplicity Studio and program it if everything is soldered correctly.