All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	cip-dev@lists.cip-project.org, felix.moessbauer@siemens.com
Subject: Re: [cip-dev][isar-cip-core][PATCH v3 0/6] Make swupdate signing more robust
Date: Wed, 13 Mar 2024 08:57:16 +0100	[thread overview]
Message-ID: <56791b55-c6ba-4fb8-84e1-ad2ceead8345@siemens.com> (raw)
In-Reply-To: <487f769c-d9c1-4071-ba45-71563eb0a411@siemens.com>



On 3/12/24 8:21 PM, Jan Kiszka wrote:
> On 12.03.24 19:50, Gylstorff Quirin wrote:
>>
>>
>> On 3/12/24 7:12 PM, Quirin Gylstorff via lists.cip-project.org wrote:
>>>
>>>
>>> On 3/12/24 9:40 AM, Jan Kiszka wrote:
>>>> On 05.03.24 17:10, Quirin Gylstorff wrote:
>>>>> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>>>>>
>>>>> This patchset adds checks to validate the certificate and key before
>>>>> used in the signing process.
>>>>>
>>>>> Add also adds the missing Documentation about swu signing in cip-core
>>>>> and fixes two issues:
>>>>>    - an error in the build logs of do_image_swu
>>>>>    - Creating all existing image recipes by touching SRC_URI in a anonym
>>>>>      python function.
>>>>>
>>>>> Changes v3:
>>>>>    - rebase onto next(704353612238cb2ac1c16f29db6f314b60cd83b0)
>>>>>    - use local variable to increase readability
>>>>>    - add formatting patches
>>>>>    - fix typo in commit message
>>>>>
>>>>> Changes v2:
>>>>>     - Add information about cpio option in long form
>>>>>     - replace cpio option `-H` with long form '--format='
>>>>>
>>>>>
>>>>> Quirin Gylstorff (6):
>>>>>     swupdate: check output of sign-swu
>>>>>     sign-swu-cms: check if key and cert are valid
>>>>>     doc: Add section about SWUpdate signing to README.swupdate.md
>>>>>     fix do not add files to each image recipe
>>>>>     format: classes/efibootguard fix spacing
>>>>>     format: classes/swupdate fix parenthesis
>>>>>
>>>>>    classes/efibootguard.bbclass                  | 39 ++++----
>>>>>    classes/swupdate.bbclass                      | 88
>>>>> +++++++++++++------
>>>>>    doc/README.swupdate.md                        | 21 +++++
>>>>>    .../swupdate-certificates/files/sign-swu-cms  | 29 +++++-
>>>>>    4 files changed, 127 insertions(+), 50 deletions(-)
>>>>>
>>>>
>>>> Thanks, applied.
>>> There is a regression on next which was not there on my integration
>>> branch. Can you please revert.
>>
>> @Jan You removed a `\` in line
>> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/blob/next/classes/swupdate.bbclass?ref_type=heads#L232 with
>> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commit/8d9e44a154ee685dc2311b7248d5f269350d2fd6
> 
> Oops, sorry, fixed now.
 >
 > Jan
 >

Ok that was the issue - the swu now contains all files again.

Thanks
Quirin


      reply	other threads:[~2024-03-13  7:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 16:10 [cip-dev][isar-cip-core][PATCH v3 0/6] Make swupdate signing more robust Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 1/6] swupdate: check output of sign-swu Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 2/6] sign-swu-cms: check if key and cert are valid Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 3/6] doc: Add section about SWUpdate signing to README.swupdate.md Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 4/6] fix do not add files to each image recipe Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 5/6] format: classes/efibootguard fix spacing Quirin Gylstorff
2024-03-05 16:10 ` [cip-dev][isar-cip-core][PATCH v3 6/6] format: classes/swupdate fix parenthesis Quirin Gylstorff
2024-03-12  8:40 ` [cip-dev][isar-cip-core][PATCH v3 0/6] Make swupdate signing more robust Jan Kiszka
2024-03-12 18:12   ` Gylstorff Quirin
2024-03-12 18:50     ` Gylstorff Quirin
2024-03-12 19:21       ` Jan Kiszka
2024-03-13  7:57         ` Gylstorff Quirin [this message]

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=56791b55-c6ba-4fb8-84e1-ad2ceead8345@siemens.com \
    --to=quirin.gylstorff@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.