Skip to content

Integrate seco-base/kirkstone/develop_sign_key

GitBot requested to merge integrate/seco-base/kirkstone/develop_sign_key/into/kirkstone/develop into kirkstone/develop

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/d59cf02d3344ac8d899e685dde8f917fc8da3ee5

[seco-setup] Rework of the RAUC custom keyring

The keyring is no longer directly copied into the recipe but rather split into the CUSTOM_KEYRING and CUSTOM_KEYRING_PATH variables. The CUSTOM_KEYRING_PATH is added as additional search path to the RAUC recipe. From there, the CUSTOM_KEYRING can be included into the image.

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/c120cb415ca686c700bee13b0df4800f18451dcb

[seco-setup] Check for empty signing key/cert path

Don't set the signing_key_path and/or the signing_cert_path in the conf_string if they are empty.

Also see 46bcbc69a09496ae919f3d7c35ea74ff7c6be6f4.

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/41aeed9ee2b9b453697add6ca349e1eb6120841d

[seco-setup] Set custom keyring for RAUC bundles

If the user uses a custom key/cert for the signing of the RAUC bundles, we also include the custom cert as keyring into the resulting image/bundle. The custom cert is used to verify future releases that are applied using the OTA feature.

--

Commit: https://git.seco.com/yocto_ng/seco-base/-/commit/affc7c73173e3c7f29c91b19980399e606002d68

[seco-config] Added config for custom signing key/cert

The key/cert can be used in the creation of custom RAUC bundles.

Merge request reports