cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel Sangorrin" <daniel.sangorrin@toshiba.co.jp>
To: jan.kiszka@siemens.com
Cc: cip-dev@lists.cip-project.org
Subject: [cip-dev] [isar-cip-core] export dpkg status for debsecan
Date: Wed, 30 Sep 2020 11:08:14 +0900	[thread overview]
Message-ID: <20200930020815.2474349-1-daniel.sangorrin@toshiba.co.jp> (raw)

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

Hi Jan,

This is a patch to isar-cip-core for exporting the dpkg 
status file which is needed by debsecan and its wrapper
cip-core-sec.

At the moment the code is duplicated for each image target.
I could use the trick of putting the code in customizations.bb
instead if you prefer, because currently it is imported from 
both image targets (cip-core-image.bb and cip-core-image-security.bb)

[isar-cip-core] image: export dpkg status file for debsecan

Thanks,
Daniel


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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5481): https://lists.cip-project.org/g/cip-dev/message/5481
Mute This Topic: https://lists.cip-project.org/mt/77210405/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-09-30  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  2:08 Daniel Sangorrin [this message]
2020-09-30  2:08 ` [cip-dev] [isar-cip-core] image: export dpkg status file for debsecan Daniel Sangorrin
2020-09-30  7:11   ` Jan Kiszka
2020-10-01  0:20     ` Daniel Sangorrin
2020-10-01  0:23     ` Daniel Sangorrin
2020-10-01  3:03     ` Daniel Sangorrin

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=20200930020815.2474349-1-daniel.sangorrin@toshiba.co.jp \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.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 NNTP newsgroup(s).