mail archive of the rauc mailing list
 help / color / mirror / Atom feed
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 14:22:21 +0100	[thread overview]
Message-ID: <da03b1b4ebdc559af079123c116d6737082f78e3.camel@pengutronix.de> (raw)
In-Reply-To: <112ee1cc577b423db517e12055d42ec3@data-modul.com>

Hi Reyhaneh,

On Fri, 2022-03-18 at 11:03 +0000, Yazdani, Reyhaneh wrote:
> > 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.
> [Reyhaneh] I asked here, since I wanted to be sure nothing has changed
> regarding implementation since six months. That is great you answered me
> quickly.

Besides the normal maintenance, most of the changes Enrico and myself are
contributing are driven by requirements from our customers (see streaming
support, encryption or the upcoming incremental block has mode).

As we don't see password support as a useful feature (there are better
alternatives avalable), it's unlikely that Pengutronix will implement this.

Best 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


      reply	other threads:[~2022-03-18 13:22 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
2022-03-18 11:03   ` Yazdani, Reyhaneh
2022-03-18 13:22     ` Jan Lübbe [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=da03b1b4ebdc559af079123c116d6737082f78e3.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