From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Alexander Dahl <ada@thorsis.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
ptxdist@pengutronix.de,
Alexander Stein <alexander.stein@systec-electronic.com>
Subject: Re: [ptxdist] [RFC PATCH] rc-once: openssh: Do not overwrite existing keys
Date: Fri, 15 Oct 2021 14:52:45 +0200 [thread overview]
Message-ID: <20211015125245.GD2239952@pengutronix.de> (raw)
In-Reply-To: <20211011125401.30402-1-ada@thorsis.com>
On Mon, Oct 11, 2021 at 02:54:01PM +0200, Alexander Dahl wrote:
> When storing your keys not in rootfs but on a separate data partition
> (using symbolic links or overlay fs), keys are overwritten on each
> firmware upgrade which lets rc-once run again (which happens when using
> opkg upgrade/update or RAUC in an A/B scheme for example).
>
> Changing keys are at best annoying, but may be interpreted as an attack
> as well.
This has come up before (I'm not sure if it was on this list or some other
channel). I'm not quite certain how to handle this.
Someone may depend on the current behavior. I think it's rather unlikely so
I'll probably ignore that but we should keep it in mind.
I'm more concerned with broken keys caused by power failures or things like
that while the keys are created. So maybe a better check than just file
existence?
> For dropbear the same behaviour was implemented with ac97e77eedf7
> ("[dropbear] rc.once: only generate keys if they aren't present yet").
Marc applied that patch. I'm probably a bit more pedantic about stuff like
that :-).
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> ---
> projectroot/etc/rc.once.d/openssh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/projectroot/etc/rc.once.d/openssh b/projectroot/etc/rc.once.d/openssh
> index 545586f07..595e28477 100644
> --- a/projectroot/etc/rc.once.d/openssh
> +++ b/projectroot/etc/rc.once.d/openssh
> @@ -27,6 +27,7 @@ create_keys() {
> hostkeys="$(get_hostkeys)" || return
>
> for keyfile in $hostkeys; do
> + [ -e "$keyfile" ] && continue
Maybe:
[ -s "$keyfile" ] && ssh-keygen -l -f "$keyfile.pub" > /dev/null && continue
A non-empty private key file and a probably valid public key should be
sufficient to prevent issues with power failures, I think.
Michael
> create_key "$keyfile" || return
> done
> }
>
> base-commit: 51994d1b518323d2975491090a2452d34b1a39f9
> --
> 2.30.2
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
--
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 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-10-15 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 12:54 Alexander Dahl
2021-10-15 12:52 ` Michael Olbrich [this message]
2021-10-15 13:22 ` Alexander Dahl
2021-10-18 6:27 ` Denis Osterland-Heim
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=20211015125245.GD2239952@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ada@thorsis.com \
--cc=alexander.stein@systec-electronic.com \
--cc=mkl@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