From: "Jan Lübbe" <jlu@pengutronix.de>
To: "Yazdani, Reyhaneh" <RYazdani@data-modul.com>,
"rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] pass PEM passphrase in Yocto build
Date: Fri, 18 Mar 2022 11:44:10 +0100 [thread overview]
Message-ID: <f97839b2ad86575da960f06660de9784a7bc02dd.camel@pengutronix.de> (raw)
In-Reply-To: <1c731e01b30146c7b24384eacf6954a9@data-modul.com>
Hi,
On Fri, 2022-03-18 at 10:32 +0000, Yazdani, Reyhaneh wrote:
> Hi everyone,
>
> I am getting the below error when I was building the bundle by Yocto with
> encrypted Root CA and ICA certificate.
>
…
> | 139843920926528:error:0906406D:PEM routines:PEM_def_callback:problems
> getting password:../openssl-1.1.1l/crypto/pem/pem_lib.c:59:
> | 139843920926528:error:0907B068:PEM routines:PEM_read_bio_PrivateKey:bad
> password read:../openssl-1.1.1l/crypto/pem/pem_pkey.c:64:
…
>
> During my investigation, I found the below post from 6 months ago:
> https://github.com/rauc/meta-rauc/issues/200
My recommendations in
https://github.com/rauc/meta-rauc/issues/200#issuecomment-943085728 still stand.
> Based on this post, I cannot use any encrypted keys and Root-CA in building a
> bundle in Yocto. Am I right?
Yes. So far, nobody has implemented support for passing a private key password
to RAUC, as the security benefits are minimal compared to the effort.
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 prev parent reply other threads:[~2022-03-18 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1c731e01b30146c7b24384eacf6954a9@data-modul.com>
2022-03-18 10:38 ` Enrico Jörns
2022-03-18 10:44 ` Jan Lübbe [this message]
2022-03-18 11:03 ` Yazdani, Reyhaneh
2022-03-18 13:22 ` Jan Lübbe
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=f97839b2ad86575da960f06660de9784a7bc02dd.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