trustfence: fix function that copies public key
Bitbake was always copying the public key 1 to the rootfs, no matter what the value specified in the 'TRUSTFENCE_KEY_INDEX' variable was. This commit fixes the issue by enclosing the variable between curly braces so that bitbake is able to expand it and calculate the correct key index. Signed-off-by: David Escalona <david.escalona@digi.com>
This commit is contained in:
parent
58b3bdb584
commit
904464c313
|
|
@ -71,7 +71,7 @@ check_gen_pki_tree() {
|
||||||
|
|
||||||
copy_public_key() {
|
copy_public_key() {
|
||||||
if [ "${DEY_SOC_VENDOR}" = "NXP" ]; then
|
if [ "${DEY_SOC_VENDOR}" = "NXP" ]; then
|
||||||
KEY_INDEX="$(expr $TRUSTFENCE_KEY_INDEX + 1)"
|
KEY_INDEX="$(expr ${TRUSTFENCE_KEY_INDEX} + 1)"
|
||||||
PUBLIC_KEY="${TRUSTFENCE_SIGN_KEYS_PATH}/crts/key${KEY_INDEX}.pub"
|
PUBLIC_KEY="${TRUSTFENCE_SIGN_KEYS_PATH}/crts/key${KEY_INDEX}.pub"
|
||||||
# The new hab/ahab_pki_tree.sh script extracts the public keys after the PKI
|
# The new hab/ahab_pki_tree.sh script extracts the public keys after the PKI
|
||||||
# generation and leaves them in the crts/ folder. However, the PKI tree may
|
# generation and leaves them in the crts/ folder. However, the PKI tree may
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue