Rotate signing keys
HERE OTA Connect has a security concept that includes signing system images with secure, offline keys. As part of the quickstart, your HERE OTA Connect account creates initial keys and stores them online. Before using HERE OTA Connect in production, however, you should create offline keys that you manage yourself, then rotate out the initial online keys.
Before you start, make sure that you’ve installed the
garage-deploy tool first. This tool includes the
garage-sign utility, which you’ll need for this procedure.
1. Rotate the TUF
1.1. Create a local TUF repository
A TUF repository is just a directory structure containing signed metadata in JSON format. Create a new one called mytufrepo with
garage-sign init --repo mytufrepo --credentials /path/to/credentials.zip
This command creates a
./tuf/mytufrepo/ directory tree in the current directory.
This directory should be secured on an encrypted filesystem.
1.2. Generate new TUF keys
There are two roles in the repo, each of which needs a new key.
garage-sign key generate --repo mytufrepo --name myroot --type rsa garage-sign key generate --repo mytufrepo --name mytargets --type rsa
1.3. Rotate the online keys with your new offline keys
This is a four-step process:
Pull the current
targets.jsonfrom OTA Connect:
garage-sign targets pull --repo mytufrepo
Perform a complete root key rotation:
garage-sign move-offline --repo mytufrepo --old-root-alias origroot \ --new-root myroot --new-targets mytargets
removes the original
rootkey from OTA Connect,
generates a new
root.jsonwith the keys generated in the previous step (
signs the new
root.jsonwith both the old and new
uploads the newly signed
root.jsonto OTA Connect
Sign the current
targets.jsonwith the new
garage-sign targets sign --repo mytufrepo --key-name mytargets
Upload the newly signed
targets.jsonto OTA Connect:
garage-sign targets push --repo mytufrepo
You have now successfully taken the TUF keys offline.
|After rotating keys, you will no longer be able to upload packages through the OTA Connect web UI—only the usual way, through bitbake.|
2. Push new images with bitbake
Export the new offline
targets into a new credentials file that you can use with
garage-sign export-credentials --repo mytufrepo --target-key-name mytargets --to offline-credentials.zip
local.conf to use the new
offline-credentials.zip file and run
bitbake as before.
As part of the
bitbake process, the image’s metadata inside
targets.json is signed with your offline TUF keys. The signed
targets.json is then uploaded to your HERE OTA Connect account.