CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [isar-cip-core][PATCH v1 2/2] swupdate.cfg.tmpl: Add digest-provider option for signature verification
Date: Mon, 20 Jul 2026 10:15:39 +0200	[thread overview]
Message-ID: <12faad9e-1d54-4c30-87cb-2279652ff72d@siemens.com> (raw)
In-Reply-To: <20260720045903.733394-3-Shivanand.Kunijadar@toshiba-tsip.com>



On 7/20/26 6:59 AM, Kunijadar Shivanand wrote:
> From: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com>
> 
> This option is introduced from v2025.12 onwards in the SWUpdate package.
> It sets the crypto backend (mbedTLS) that the SWUpdate uses to verify
> signed updates and compute digests when multiple provides are available.
> 
> Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com>
> ---
>   .../files/{swupdate.cfg => swupdate.cfg.tmpl}             | 1 +
>   recipes-core/swupdate-config/swupdate-config_0.2.bb       | 8 +++++---
>   2 files changed, 6 insertions(+), 3 deletions(-)
>   rename recipes-core/swupdate-config/files/{swupdate.cfg => swupdate.cfg.tmpl} (77%)
> 
> diff --git a/recipes-core/swupdate-config/files/swupdate.cfg b/recipes-core/swupdate-config/files/swupdate.cfg.tmpl
> similarity index 77%
> rename from recipes-core/swupdate-config/files/swupdate.cfg
> rename to recipes-core/swupdate-config/files/swupdate.cfg.tmpl
> index 3e2b45c..44d8d04 100644
> --- a/recipes-core/swupdate-config/files/swupdate.cfg
> +++ b/recipes-core/swupdate-config/files/swupdate.cfg.tmpl
> @@ -2,4 +2,5 @@ globals :
>   {
>       bootloader = "ebg";
>       public-key-file = "/usr/share/swupdate-signing/swupdate-sign.crt"
here is semicolon missing.
> +    ${SWUPDATE_DIGEST_PROVIDER}
>   };
> diff --git a/recipes-core/swupdate-config/swupdate-config_0.2.bb b/recipes-core/swupdate-config/swupdate-config_0.2.bb
> index b48e3d1..584706c 100644
> --- a/recipes-core/swupdate-config/swupdate-config_0.2.bb
> +++ b/recipes-core/swupdate-config/swupdate-config_0.2.bb
> @@ -19,12 +19,14 @@ DEBIAN_PROVIDES := "${PN}"
>   
>   PN .= "-${MACHINE}"
>   
> -SRC_URI = "file://swupdate.cfg \
> +SRC_URI = "file://swupdate.cfg.tmpl \
>              file://hwrevision.tmpl"
>   
> +SWUPDATE_DIGEST_PROVIDER ??= ""
> +SWUPDATE_DIGEST_PROVIDER:sid = "digest-provider = "pkcs#7mbedtls";"

It would be better to pin the version for the previous versions instead 
of sid.

Quirin

>   MACHINE_HW_VERSION ??= "cip-core-1.0"
> -TEMPLATE_FILES += "hwrevision.tmpl"
> -TEMPLATE_VARS += "MACHINE MACHINE_HW_VERSION"
> +TEMPLATE_FILES += "hwrevision.tmpl swupdate.cfg.tmpl"
> +TEMPLATE_VARS += "MACHINE MACHINE_HW_VERSION SWUPDATE_DIGEST_PROVIDER"
>   
>   do_install[cleandirs] = "${D}/etc/"
>   do_install() {
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#23670): https://lists.cip-project.org/g/cip-dev/message/23670
> Mute This Topic: https://lists.cip-project.org/mt/120354799/1753640
> Group Owner: cip-dev+owner@lists.cip-project.org
> Unsubscribe: https://lists.cip-project.org/g/cip-dev/unsub [quirin.gylstorff@siemens.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  reply	other threads:[~2026-07-20  8:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  4:59 [isar-cip-core][PATCH v1 0/2] Enable SWUpdate support for Debian sid Shivanand.Kunijadar
2026-07-20  4:59 ` [isar-cip-core][PATCH v1 1/2] swupdate-handler-roundrobin: Keep Lua version 5.5 for sid Shivanand.Kunijadar
2026-07-20  8:14   ` [cip-dev] " Quirin Gylstorff
2026-07-20  4:59 ` [isar-cip-core][PATCH v1 2/2] swupdate.cfg.tmpl: Add digest-provider option for signature verification Shivanand.Kunijadar
2026-07-20  8:15   ` Quirin Gylstorff [this message]
2026-07-20  8:13 ` [cip-dev] [isar-cip-core][PATCH v1 0/2] Enable SWUpdate support for Debian sid Quirin Gylstorff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12faad9e-1d54-4c30-87cb-2279652ff72d@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox