From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [RFC PATCH 1/1] image-postproc-extension: remove ssh-host-keys
Date: Thu, 16 Apr 2020 12:17:44 +0200 [thread overview]
Message-ID: <20200416101744.3bjlmwn35bjopz5d@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20200313134028.28650-2-Quirin.Gylstorff@siemens.com>
Hello Quirin,
On Fri, Mar 13, 2020 at 02:40:28PM +0100, Q. Gylstorff wrote:
> Add the option to remove all ssh_host_keys during image_postprocessing.
> This ensures that images with read-only rootfs or overlays use the
> keys generated during the image generation.
>
> sshd-regen-keys: create new ssh keys if the keys do not exit
The change makes sense to me. Normally I prefer static generation, but this
isn't possible, since the image should be flashed to multiple devices. In that
case, keeping keys in the image doesn't make sense.
Given that, should this be an IMAGE_FEATURE? Does anything speak against always
removing the sshd keys during the image generation? Opinions welcome.
If it remains an IMAGE_FEATURE, I think we should describe it in the user
manual.
Regarding the patch: We've fixed the following issues, I'll send a v2
suggestion.
* Commit comment: "exit" -> "exist".
* Inconsistent indentation in meta/classes/image-postproc-extension.bbclass:
Fixed to 4.
* meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh: echo "Removing
keys ..." doesn't apply anymore: Removed.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-04-16 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 13:40 [RFC PATCH 0/1] Remove ssh-keys in postprocessing Q. Gylstorff
2020-03-13 13:40 ` [RFC PATCH 1/1] image-postproc-extension: remove ssh-host-keys Q. Gylstorff
2020-04-16 10:17 ` Baurzhan Ismagulov [this message]
2020-04-16 10:20 ` [PATCH] image-postproc-extension: Remove ssh-host-keys Baurzhan Ismagulov
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=20200416101744.3bjlmwn35bjopz5d@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.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