mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 5/5] ptxd_lib_code_signing: add key whitelist checks
Date: Sun, 12 Sep 2021 22:33:29 +0200	[thread overview]
Message-ID: <20210912203329.pc3e5dc6lylbntq7@pengutronix.de> (raw)
In-Reply-To: <20210908114359.ik54f4ufg44gq2bb@pengutronix.de>

On Wed, Sep 08, 2021 at 01:43:59PM +0200, Roland Hieber wrote:
> On Fri, Sep 03, 2021 at 03:17:13PM +0200, Michael Olbrich wrote:
> > On Mon, Aug 09, 2021 at 10:06:08AM +0200, Roland Hieber wrote:
> > > diff --git a/rules/pre/030-code-signing-consumers.make b/rules/pre/030-code-signing-consumers.make
> > > index 909e8ebd6936..bca05854372d 100644
> > > --- a/rules/pre/030-code-signing-consumers.make
> > > +++ b/rules/pre/030-code-signing-consumers.make
> > > @@ -28,6 +28,9 @@ $(strip \
> > >  		$(call ptx/cs-consumer-env, $(1))\
> > >  			cs_get_uri '$(strip $(2))'\
> > >  	)\
> > > +	$(if $(filter-out 0,$(.SHELLSTATUS)),\
> > > +		$(call ptx/error, cs-get-uri: whitelist check failed – see errors above)\
> > > +	)\
> > 
> > You cannot use ptx/error here. That macro can only be used for stuff that
> > is evaluated before the first target is executed. Otherwise the error
> > message will get lost.
> > You need to use $(error ...) here. Probably with the same $(shell :) hack
> > that is used in kernel.make.
> 
> Okay.

The $(shell :) hack was apparently not necessary, but there was some
fallout; as soon as I changed it to $(error), I noticed that it errors
all over the place when building a BSP from scratch, so I had to make a
few more fixes for variables that are expanded before the code signing
provider is installed.

> > >  )
> > >  endef
> > >  
> > > @@ -40,5 +43,8 @@ $(strip \
> > >  		$(call ptx/cs-consumer-env, $(1))\
> > >  			cs_get_ca '$(strip $(2))'\
> > >  	)\
> > > +	$(if $(filter-out 0,$(.SHELLSTATUS)),\
> > > +		$(call ptx/error, cs-get-ca: whitelist check failed – see errors above)\
> > > +	)\
> > 
> > same here.

 - Roland


-- 
Roland Hieber, Pengutronix e.K.          | r.hieber@pengutronix.de     |
Steuerwalder Str. 21                     | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686         | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

  reply	other threads:[~2021-09-12 20:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09  8:06 [ptxdist] [PATCH v2 1/5] ptxd_make_world_common: make the package name available to scripts Roland Hieber
2021-08-09  8:06 ` [ptxdist] [PATCH v2 2/5] libptxdist: introduce ptxd_exec_silent_stderr Roland Hieber
2021-08-09  8:06 ` [ptxdist] [PATCH v2 3/5] ptxd_lib_code_signing: refactor hard-coded SoftHSM PIN in PKCS11 URIs Roland Hieber
2021-09-03 12:46   ` Michael Olbrich
2021-09-08 11:27     ` Roland Hieber
2021-09-08 14:01       ` Michael Olbrich
2021-08-09  8:06 ` [ptxdist] [PATCH v2 4/5] ptxd_lib_code_signing: provide consumer functions with some environment Roland Hieber
2021-09-03 12:54   ` Michael Olbrich
2021-09-08 11:30     ` Roland Hieber
2021-09-08 14:08       ` Michael Olbrich
2021-09-08 20:53   ` Roland Hieber
2021-08-09  8:06 ` [ptxdist] [PATCH v2 5/5] ptxd_lib_code_signing: add key whitelist checks Roland Hieber
2021-08-09  9:30   ` Roland Hieber
2021-09-03 13:17   ` Michael Olbrich
2021-09-08 11:43     ` Roland Hieber
2021-09-12 20:33       ` Roland Hieber [this message]
2021-09-29 11:51         ` Michael Olbrich
2021-09-03 12:48 ` [ptxdist] [PATCH v2 1/5] ptxd_make_world_common: make the package name available to scripts Michael Olbrich
2021-09-08 10:17   ` Roland Hieber

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=20210912203329.pc3e5dc6lylbntq7@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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