From: Michael Olbrich <mol@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] rauc: fix previous private key location triggering key creation message
Date: Tue, 06 Oct 2020 10:18:50 +0200 [thread overview]
Message-ID: <E1kPiBO-0005Uh-Ey@dude02.hi.pengutronix.de> (raw)
In-Reply-To: <20200924104811.30246-1-bst@pengutronix.de>
Thanks, applied as 22771878dc0dffd45b44346147ba0fb828cd33e6.
Michael
[sent from post-receive hook]
On Tue, 06 Oct 2020 10:18:50 +0200, Bastian Krause <bst@pengutronix.de> wrote:
> Prior to the code signing infrastructure introduction, 001a500ed
> ("scripts: add script that generates test certificates for RAUC")
> suggested to move the private key to
> <platform-dir>/config/rauc/rauc.key.pem. This is the location that
> should be checked for key material.
>
> Fixes: c420c0745 ("rauc/image-rauc: use code signing infrastructure for key retrieval")
> Signed-off-by: Bastian Krause <bst@pengutronix.de>
> Message-Id: <20200924104811.30246-1-bst@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/rauc.make b/rules/rauc.make
> index c1cba47e9dd0..75a7d35212cd 100644
> --- a/rules/rauc.make
> +++ b/rules/rauc.make
> @@ -48,7 +48,7 @@ RAUC_CONF_OPT := \
>
> $(STATEDIR)/rauc.prepare:
> @$(call targetinfo)
> - @test ! -e "$(call ptx/in-platformconfigdir, config/rauc/rauc.key)" || \
> + @test ! -e "$(call ptx/in-platformconfigdir, config/rauc/rauc.key.pem)" || \
> ptxd_bailout "Please use the signing provider infrastructure desribed in:" \
> "https://www.ptxdist.org/doc/dev_code_signing.html"
> @$(call world/prepare, RAUC)
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2020-10-06 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 10:48 [ptxdist] [PATCH] " Bastian Krause
2020-10-06 8:18 ` Michael Olbrich [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=E1kPiBO-0005Uh-Ey@dude02.hi.pengutronix.de \
--to=mol@pengutronix.de \
--cc=bst@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