mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bastian Krause <bst@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: [ptxdist] [PATCH] rauc: fix previous private key location triggering key creation message
Date: Thu, 24 Sep 2020 12:48:11 +0200	[thread overview]
Message-ID: <20200924104811.30246-1-bst@pengutronix.de> (raw)

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>
---
 rules/rauc.make | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rules/rauc.make b/rules/rauc.make
index c1cba47e9..75a7d3521 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)
-- 
2.28.0


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

             reply	other threads:[~2020-09-24 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 10:48 Bastian Krause [this message]
2020-10-06  8:18 ` [ptxdist] [APPLIED] " Michael Olbrich

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=20200924104811.30246-1-bst@pengutronix.de \
    --to=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