All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: "Moessbauer, Felix (T CED OES-DE)" <felix.moessbauer@siemens.com>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"Kiszka, Jan (T CED)" <jan.kiszka@siemens.com>
Subject: Re: [cip-dev][isar-cip-core][PATCH 0/4] Make swupdate signing more
Date: Mon, 4 Mar 2024 17:26:17 +0100	[thread overview]
Message-ID: <54be3372-25b0-4ef6-8d1d-4fb045a193a8@siemens.com> (raw)
In-Reply-To: <73e61f626f9f5530afcefb93af6d626f7f6087af.camel@siemens.com>



On 3/4/24 2:36 PM, Moessbauer, Felix (T CED OES-DE) wrote:
> On Mon, 2024-03-04 at 11:08 +0100, 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.
>>
>> Quirin Gylstorff (4):
>>    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
> 
> Where is this patch? Looks like it did not make it onto the list.

Should have I will resend it.
Quirin
> 
> Felix
> 
>>
>>   classes/efibootguard.bbclass                  |  1 -
>>   classes/swupdate.bbclass                      | 83 +++++++++++++----
>> --
>>   doc/README.swupdate.md                        | 21 +++++
>>   .../swupdate-certificates/files/sign-swu-cms  | 29 ++++++-
>>   4 files changed, 105 insertions(+), 29 deletions(-)
>>
> 


  reply	other threads:[~2024-03-04 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 10:08 [cip-dev][isar-cip-core][PATCH 0/4] Make swupdate signing more Quirin Gylstorff
2024-03-04 10:08 ` [cip-dev][isar-cip-core][PATCH 1/4] swupdate: check output of sign-swu Quirin Gylstorff
2024-03-04 13:42   ` MOESSBAUER, Felix
2024-03-04 16:30     ` Gylstorff Quirin
2024-03-04 10:08 ` [cip-dev][isar-cip-core][PATCH 2/4] sign-swu-cms: check if key and cert are valid Quirin Gylstorff
2024-03-04 13:38   ` MOESSBAUER, Felix
2024-03-04 10:08 ` [cip-dev][isar-cip-core][PATCH 3/4] doc: Add section about SWUpdate signing to README.swupdate.md Quirin Gylstorff
2024-03-04 13:36 ` [cip-dev][isar-cip-core][PATCH 0/4] Make swupdate signing more MOESSBAUER, Felix
2024-03-04 16:26   ` Gylstorff Quirin [this message]
2024-03-04 16:27 ` [cip-dev][isar-cip-core][PATCH 4/4] fix do not add files to each image recipe Quirin Gylstorff
2024-03-05  6:23 ` [cip-dev][isar-cip-core][PATCH 0/4] Make swupdate signing more Jan Kiszka

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=54be3372-25b0-4ef6-8d1d-4fb045a193a8@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.