From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Cc: Ross Burton <ross.burton@arm.com>, Jon Mason <Jon.Mason@arm.com>
Subject: Re: [OE-core] [PATCH] ssh-pregen-hostkeys: Limit to qemu machines by default
Date: Thu, 09 May 2024 12:53:00 +0100 [thread overview]
Message-ID: <c98fa269df5aa2b7a7cae7c1110ea8eb2c07ba3d.camel@linuxfoundation.org> (raw)
In-Reply-To: <17CDCFA3A4D0E385.8965@lists.openembedded.org>
On Thu, 2024-05-09 at 12:48 +0100, Richard Purdie via lists.openembedded.org wrote:
> There are potential security issues from using pre-generated host keys. We made
> the recipe available for autobuilder testing purposes but concerns remain about
> how easily this could end up in production.
>
> I thought we'd already done this, but limit the recipe to qemu* machines,
> which means any real hardware trying to use it will need to be a bit more
> explicit about it and specifically enable it.
* This change may require some BSPs to opt into the recipe such as
fvp-base in meta-arm. Given the security concerns around this, that
does seem like a reasonable compromise though.
Cheers,
Richard
parent reply other threads:[~2024-05-09 11:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <17CDCFA3A4D0E385.8965@lists.openembedded.org>]
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=c98fa269df5aa2b7a7cae7c1110ea8eb2c07ba3d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Jon.Mason@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).