All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Kiszka" <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org,
	Venkata Pyla <venkata.pyla@toshiba-tsip.com>
Subject: Re: [cip-dev] [isar-cip-core 1/3] cip-security: Add packages for IEC-62443-4-2 evaluation
Date: Wed, 29 Jul 2020 18:42:45 +0200	[thread overview]
Message-ID: <37d1e0f2-825e-e833-2b05-ec84cc3decbf@siemens.com> (raw)
In-Reply-To: <7345.1596026360263349677@lists.cip-project.org>

[-- Attachment #1: Type: text/plain, Size: 2898 bytes --]

On 29.07.20 14:39, Venkata Pyla wrote:
> On Mon, Jul 27, 2020 at 08:04 PM, Jan Kiszka wrote:
> 
>>
>> On 27.07.20 13:41, venkata.pyla@toshiba-tsip.com wrote:
>>> From: Kazuhiro Hayashi <kazuhiro3.hayashi@toshiba.co.jp>
>>>
>>> Identified security packages are added to the target image
>>> and that will be used for IEC-62443-4-2 evaluation
>>>
>>> Signed-off-by: Kazuhiro Hayashi <kazuhiro3.hayashi@toshiba.co.jp>
>>> Signed-off-by: Venkata Pyla <venkata.pyla@toshiba-tsip.com>
>>> ---
>>>    .../images/cip-core-image-security.bb         | 36 +++++++++++++++++++
>>>    1 file changed, 36 insertions(+)
>>>    create mode 100644 recipes-core/images/cip-core-image-security.bb
>>>
>>> diff --git a/recipes-core/images/cip-core-image-security.bb
>> b/recipes-core/images/cip-core-image-security.bb
>>> new file mode 100644
>>> index 0000000..a17c522
>>> --- /dev/null
>>> +++ b/recipes-core/images/cip-core-image-security.bb
>>> @@ -0,0 +1,36 @@
>>> +#
>>> +# A reference image which includes security packages
>>> +#
>>> +# Copyright (c) Toshiba Corporation, 2020
>>> +#
>>> +# Authors:
>>> +#  Kazuhiro Hayashi <kazuhiro3.hayashi@toshiba.co.jp>
>>> +#
>>> +# SPDX-License-Identifier: MIT
>>> +#
>>> +
>>> +inherit image
>>> +
>>> +DESCRIPTION = "CIP Core image including security packages"
>>> +
>>> +IMAGE_INSTALL += "customizations"
>>> +
>>> +# Debian packages that provide security features
>>> +IMAGE_PREINSTALL += " \
>>> +	openssl libssl1.1 \
>>> +	fail2ban \
>>> +	openssh-server openssh-sftp-server openssh-client \
>>> +	syslog-ng-core syslog-ng-mod-journal \
>>> +	aide aide-common \
>>> +	libnftables0 nftables \
>>> +	libpam-pkcs11 \
>>> +	chrony \
>>> +	tpm2-tools \
>>> +	tpm2-abrmd \
>>> +	libtss2-esys0 libtss2-udev \
>>> +	libpam-cracklib \
>>> +	acl \
>>> +	libauparse0 audispd-plugins auditd \
>>> +	uuid-runtime \
>>> +	sudo \
>>> +"
>>>
>>
>> Still no CI for this. You can send that separately on top, the series
>> looks fine otherwise.
>>
> 
> To add security image in gitlab-ci.yml i need some suggestions...
> in deploy-cip-core script that is used in gitlab-ci is expecting *.wic image for copying the files,
> but because there is no wks file yet for QEMU it is not generating the image.
> 
> i think we should add wks file for the qemu target, can you guide me how to do that?

Such a wks file only makes sense when we switch QEMU to image-based 
booting, like Quirin does in [1].

For adding CI coverage to the security image, it would already be enough 
to just build it, skipping the deployment. Of course, if you'd like to 
feed the build result into automated testing, that needs deployment 
again, but possibly also more. So, let's postpone it until that is on 
the agenda of the day, I would say.

Jan

[1] https://lists.cip-project.org/g/cip-dev/message/4997

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5047): https://lists.cip-project.org/g/cip-dev/message/5047
Mute This Topic: https://lists.cip-project.org/mt/75820361/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2020-07-29 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 11:41 [cip-dev] [isar-cip-core 0/3] Security Branch patches Venkata Pyla
2020-07-27 11:41 ` [cip-dev] [isar-cip-core 1/3] cip-security: Add packages for IEC-62443-4-2 evaluation Venkata Pyla
2020-07-27 14:34   ` Jan Kiszka
2020-07-29 12:39     ` Venkata Pyla
2020-07-29 16:42       ` Jan Kiszka [this message]
2020-07-27 11:41 ` [cip-dev] [isar-cip-core 2/3] start-qemu.sh: Use 'TARGET_IMAGE' to pick respective image file Venkata Pyla
2020-07-27 11:41 ` [cip-dev] [isar-cip-core 3/3] README: Add steps to build cip-security image Venkata Pyla
2020-07-29 16:57 ` [cip-dev] [isar-cip-core 0/3] Security Branch patches Jan Kiszka

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=37d1e0f2-825e-e833-2b05-ec84cc3decbf@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=venkata.pyla@toshiba-tsip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.