public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@isar-build.org>
To: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCHv2 1/2] meta/classes/image: Introduce sshd host key assertion
Date: Mon, 10 Jun 2019 18:19:35 +0200	[thread overview]
Message-ID: <082c2e71-3352-3c5e-d49c-8da032a71cb9@isar-build.org> (raw)
In-Reply-To: <20190603131231.578a081d@md1za8fc.ad001.siemens.net>

On 6/3/19 1:12 PM, Henning Schild wrote:
> Change to v1:
>    - use find instead of "ls *" to detect if there are any keys
>    - reduce to just one if statement
> 
> Henning

Rebased and applied to the 'next'.

Regards,
Maxim.

> Am Mon, 3 Jun 2019 13:10:59 +0200
> schrieb Henning Schild <henning.schild@siemens.com>:
> 
>> From: Henning Schild <henning.schild@siemens.com>
>>
>> Images containing ssh host keys without some way of dealing with the
>> fact that those have to be generate at run-time not install-time are
>> invalid!
>>
>> Introduce a check that our own package "sshd-regen-keys" is installed
>> when such keys are present (when an ssh daemon is installed).
>>
>> Suggest to install that package or find some other way of dealing with
>> the problem. But fail by default, since such an image is most likely
>> broken.
>>
>> Signed-off-by: Henning Schild <henning.schild@siemens.com>
>> ---
>>   meta/classes/image-postproc-extension.bbclass | 13 +++++++++++++
>>   1 file changed, 13 insertions(+)
>>
>> diff --git a/meta/classes/image-postproc-extension.bbclass
>> b/meta/classes/image-postproc-extension.bbclass index
>> 625ba7d..f6ed793 100644 ---
>> a/meta/classes/image-postproc-extension.bbclass +++
>> b/meta/classes/image-postproc-extension.bbclass @@ -44,3 +44,16 @@
>> image_postprocess_mark() { update_etc_os_release \
>>           --build-id "${BUILD_ID}" --variant "${DESCRIPTION}"
>>   }
>> +
>> +ROOTFS_POSTPROCESS_COMMAND =+ "image_postprocess_sshd_key_regen"
>> +
>> +image_postprocess_sshd_key_regen() {
>> +    nhkeys=$( find ${IMAGE_ROOTFS}/etc/ssh/ -iname "ssh_host_*key*"
>> -printf '.' | wc -c )
>> +    if [ $nhkeys -ne 0 -a ! -d
>> ${IMAGE_ROOTFS}/usr/share/doc/sshd-regen-keys ]; then
>> +       bbwarn "Looks like you have ssh host keys in the image but
>> did "\
>> +              "not install \"sshd-regen-keys\". This image should
>> not be "\
>> +              "deployed more than once."
>> +       bberror "Install the package or forcefully remove this check!"
>> +       exit 1
>> +    fi
>> +}
> 


      reply	other threads:[~2019-06-10 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 11:10 Henning Schild
2019-06-03 11:11 ` [PATCHv2 2/2] rpi-stretch: install sshd-regen-keys since openssh-server is inside Henning Schild
2019-06-03 11:12 ` [PATCHv2 1/2] meta/classes/image: Introduce sshd host key assertion Henning Schild
2019-06-10 16:19   ` Maxim Yu. Osipov [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=082c2e71-3352-3c5e-d49c-8da032a71cb9@isar-build.org \
    --to=mosipov@isar-build.org \
    --cc=henning.schild@siemens.com \
    --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