Skip to content

Commit b9dd88a

Browse files
committed
chore(docs) add docs how to generate keys
This patch updates HOWTO docs with how to generate the private keys. Signed-off-by: Kenjiro Nakayama <nakayamakenjiro@gmail.com>
1 parent 650c86a commit b9dd88a

1 file changed

Lines changed: 9 additions & 3 deletions

File tree

HOWTO.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -681,9 +681,15 @@ identification with the Manufacturing server.
681681
Identification keys, valid values: `filesystem` (`tpm` not yet
682682
implemented).
683683

684-
3. `DI_SIGN_KEY_PATH`:
685-
686-
4. `DI_HMAC_KEY_PATH`:
684+
3. `DI_SIGN_KEY_PATH`: filepath to the private key with DER format.
685+
For example, you can create the key file with `openssl` command:
686+
```sh
687+
$ openssl ecparam -name secp384r1 -genkey -noout -outform der -out /path/to/sign_key/key.der
688+
```
689+
Please note that the curve `secp384r1` must match to the `key_type` specified in `manufacturing_server.yaml`.
690+
691+
4. `DI_HMAC_KEY_PATH`: filepath to the HMAC key. There is no format limitation,
692+
you can use the file with random value.
687693

688694
5. `DEVICE_CREDENTIAL_FILENAME`: [optional] filepath specified by the user to
689695
store the device credentials, by default `/etc/device-credentials`.

0 commit comments

Comments
 (0)