From: "Jan Lübbe" <jlu@pengutronix.de>
To: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>,
"rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] RAUC update systems with release keys
Date: Mon, 14 Mar 2022 09:39:13 +0100 [thread overview]
Message-ID: <795a88c90d228b8e234fbc2831daf08d050145ad.camel@pengutronix.de> (raw)
In-Reply-To: <b098c3e50a5549f984c64e4197f80dd1@data-modul.com>
Hi Reyhaneh,
On Mon, 2022-03-14 at 08:08 +0000, Yazdani, Reyhaneh wrote:
> Hello,
>
> Currently we have some devices which are programmed with development keys in
> the past.
> Now, we need to use them as final devices with bundle signed with release
> keys.
> I copied cert file manually to the certificate path in rootfs and try to use
> rauc install command to program the device with release-bundle, but it fails.
Just to avoid misunderstandings: You replaced your /etc/rauc/keyring.pem (or
another keyring path as configured in your system.com) with the release keyring?
Did you restart the rauc service?
> What would be the correct procedure to bring development-devices into final-
> devices?
Your approach should work in general, but there are others.
You could also have the release CA certificate as a second cert in the
development image keyring. In that case, you should be careful with migrations,
though, as you probably want to avoid unexpected leftovers from development
software.
Regards,
Jan
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
next parent reply other threads:[~2022-03-14 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b098c3e50a5549f984c64e4197f80dd1@data-modul.com>
2022-03-14 8:39 ` Jan Lübbe [this message]
2022-03-14 9:40 ` Yazdani, Reyhaneh
2022-03-14 10:25 ` Jan Lübbe
2022-03-14 11:01 ` Yazdani, Reyhaneh
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=795a88c90d228b8e234fbc2831daf08d050145ad.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=RYazdani@data-modul.com \
--cc=rauc@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