public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
To: jan.kiszka@siemens.com
Cc: isar-users@googlegroups.com
Subject: [debsecan] export dpkg status for debsecan
Date: Thu,  1 Oct 2020 14:06:34 +0900	[thread overview]
Message-ID: <20201001050635.2880259-1-daniel.sangorrin@toshiba.co.jp> (raw)

Hello,

This patch causes rootfs builds to export the /var/lib/dpkg/status
file, which is required for debsecan to scan vulnerabilities. It is
very similar to what generate-manifest does already, it is just
that debsecan needs this file format.

I have tested it by building [isar-cip-core](https://gitlab.com/cip-project/cip-core/isar-cip-core)
QEMU images and it works fine, however I couldn't (didn't know how to) test SDK creation because
we are not using that feature yet.

[debsecan] meta/classes: export dpkg status file for debsecan

Thanks,
Daniel


             reply	other threads:[~2020-10-01  5:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01  5:06 Daniel Sangorrin [this message]
2020-10-01  5:06 ` [debsecan] meta/classes: export dpkg status file " Daniel Sangorrin
2020-10-05  6:06   ` Jan Kiszka
2020-10-05 15:21   ` Baurzhan Ismagulov
2020-11-26 17:18   ` Anton Mikanovich

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=20201001050635.2880259-1-daniel.sangorrin@toshiba.co.jp \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=isar-users@googlegroups.com \
    --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