Skip to content

milkylainen/stm32mp1sign

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

stm32mp1sign

Raison d'être: Signing stm32mp1 headers is a STM closed source affair. The signing tool is part of a large software package (CubeProgrammer). And it is very cumbersome to try to integrate in a normal build environment. But fortunately, all is needed is some plain cryptography. stm32mp1sign is written in C and uses openssl.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

stm32mp1sign is a C replacement for STM32MP_SigningTool_CLI (closed source) in STM32CubeProgrammer. It is currently only capable of handling stm32 v1 headers present in the stm32mp15x series.

Functionally implemented from the descriptions at:

STM32MP1 Secure Boot Description

STM32MP1 KeyGen Tool Description

STM32MP1 STM32Key U-Boot Command

STM32MP1 Sign Tool Description

Beware. Fusing a device means you can never undo the key. If you loose the private key or password, then that's it. No more signing new images. If you also close the device then there will be no other way out. You have been warned!

  1. Generate keys. Here you can use STM32CubeProgrammer or regular OpenSSL. This should get you a prime256v1 (default) curve key with the privkey encrypted in AES256 (default). DO NOT LOOSE THE KEYS!

$ ./STM32MP_KeyGen_CLI -abs /home/user/KeyFolder/ -pwd qwerty

or

$ openssl ecparam -name prime256v1 -genkey -noout -out privateKey.pem
$ openssl ec -in privateKey.pem -pubout -out publicKey.pem

  1. You can now use stm32mp1sign to sign your TF-A (fsbl) binary. Using stm32mp1sign, the image is modified in situ. The key path must contain a private key with a public key included. If a password is not specified, stm32mp1sign will ask for one.

$ stm32mp1sign --image path/to/tf-a-binary --key path/to/privkey --sign --password qwerty

  1. You can also use stm32mp1sign to verify you TF-A (fsbl) binary. The key path must contain a public key. You can amend the option --pubhash. It outputs a sha256 hash of the public key raw ecpoints in a file. The usage of --pubhash is not mandatory.

$ stm32mp1sign --image path/to/tf-a-binary --key path/to/pubkey --verify --pubhash

  1. Copy the hash of the public key to U-boot and fuse it there. (WARNING!)

> tftpboot 0xc0000000 publicKeyHash.bin
> stm32key read 0xc0000000
> stm32key fuse 0xc0000000