meta-digi/meta-digi-arm/recipes-bsp/trustfence-cst
Hector Palacios 998598415a dey-image: generate public key after rootfs install
When TrustFence is enabled, a PKI tree is generated.
In the case of NXP platforms, the PKI contains public certificates
from which the public key needs to be extracted using an openssl
command.
In the case of STM platforms, the PKI contains directly the
public key.

In all cases, we need the public key to be installed in the
rootfs /etc/ssl/certs/ folder, so that it can be used by
swupdate to authenticate signed SWU packages.
Up to now, this was being done on the dualboot recipe, but the
installation of the public key should really be only dependant
on the fact of TF being enabled.

This commit:
 - Removes the generation of the public key from dualboot.bb.
 - Generates a patch to extract the public key from the certificate
   as part of the PKI tree generation (on NXP platforms).
 - Installs the public key during a post install function after
   the final rootfs has been created.
 - For NXP platforms, extracts the public key using openssl if
   it does not exist (for backwards compatibility).

Signed-off-by: Hector Palacios <hector.palacios@digi.com>
2023-08-21 09:21:30 +02:00
..
trustfence-cst dey-image: generate public key after rootfs install 2023-08-21 09:21:30 +02:00
nativesdk-trustfence-cst_3.3.1.bb trustfence-cst: restrict package to native/nativesdk 2022-07-06 11:58:57 +02:00
trustfence-cst-3.3.1.inc dey-image: generate public key after rootfs install 2023-08-21 09:21:30 +02:00
trustfence-cst-native_3.3.1.bb trustfence-cst: restrict package to native/nativesdk 2022-07-06 11:58:57 +02:00