From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 3/3] Separate apt-key entries from default keyring
Date: Wed, 27 Feb 2019 17:14:43 +0100 [thread overview]
Message-ID: <20190227171443.7bb07fc2@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190227151856.11594-4-andreas.reichel.ext@siemens.com>
Is this fixing an issue introduced in p1? I guess you should just
squash it ;).
Henning
Am Wed, 27 Feb 2019 16:18:56 +0100
schrieb "[ext] Andreas J. Reichel" <andreas.reichel.ext@siemens.com>:
> From: Andreas Reichel <andreas.reichel.ext@siemens.com>
>
> Per default, apt-key add adds keys to /etc/apt/trusted.gpg.
> However, when building without a container, we don't want to
> contaminate the host. Therefore, we specify a keyring file
> in /etc/apt/trusted.gpg.d directory named `isar.gpg`. This file can
> be deleted after the build.
>
> This is necessary because we don't want to specify single keyrings
> to debootstrap since we might need a mixture of several keyrings
> as per default and would have to find all needed keyrings on the
> system, export their keys and reimport into the build keyring, which
> is more complicated and unneeded this way.
>
> Signed-off-by: Andreas Reichel <andreas.reichel.ext@siemens.com>
> ---
> meta/classes/isar-bootstrap-helper.bbclass | 1 +
> meta/classes/isar-image.bbclass | 1 +
> meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb | 2 +-
> meta/recipes-core/isar-bootstrap/isar-bootstrap.inc | 2 +-
> 4 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/isar-bootstrap-helper.bbclass
> b/meta/classes/isar-bootstrap-helper.bbclass index 26abf62..769cbef
> 100644 --- a/meta/classes/isar-bootstrap-helper.bbclass
> +++ b/meta/classes/isar-bootstrap-helper.bbclass
> @@ -22,6 +22,7 @@ HOST_DISTRO ?= "debian-stretch"
> HOST_ARCH ?= "${@get_deb_host_arch()}"
>
> HOST_DISTRO_APT_SOURCES += "conf/distro/${HOST_DISTRO}.list"
> +ISARKEYRING = "/etc/apt/trusted.gpg.d/isar.gpg"
>
> def reverse_bb_array(d, varname):
> array = d.getVar(varname, True)
> diff --git a/meta/classes/isar-image.bbclass
> b/meta/classes/isar-image.bbclass index cdd1651..4a89bd7 100644
> --- a/meta/classes/isar-image.bbclass
> +++ b/meta/classes/isar-image.bbclass
> @@ -82,6 +82,7 @@ isar_image_cleanup() {
> fi
> rm -f "${IMAGE_ROOTFS}/etc/apt/sources-list"
> '
> + sudo rm -f "${ISARKEYRING}"
> }
>
> do_rootfs() {
> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb index
> a793585..b70d2a8 100644 ---
> a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb +++
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb @@ -11,8
> +11,8 @@ WORKDIR =
> "${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PN}-${HOST_DISTRO}-${HOST_A
> DEPLOY_ISAR_BOOTSTRAP =
> "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}"
> ISAR_BOOTSTRAP_LOCK =
> "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}.lock" -require
> isar-bootstrap.inc inherit isar-bootstrap-helper +require
> isar-bootstrap.inc do_generate_keyring[stamp-extra-info] =
> "${DISTRO}-${DISTRO_ARCH}"
> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc index
> 2ef3b1e..4613732 100644 ---
> a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc +++
> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc @@ -179,7
> +179,7 @@ do_generate_keyring() { chmod 777 "${APTKEYTMPDIR}"
> for keyfile in ${@d.getVar("APTKEYFILES", True)}; do
> cp "$keyfile" "${APTKEYTMPDIR}"/"$(basename "$keyfile")"
> - sudo apt-key add "$keyfile"
> + sudo apt-key --keyring "${ISARKEYRING}" add "$keyfile"
> done
> fi
> }
next prev parent reply other threads:[~2019-02-27 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 15:18 [PATCH v2 0/3] Fixes usage of additional apt keys Andreas J. Reichel
2019-02-27 15:18 ` [PATCH v2 1/3] Fix and simplify apt keyring generation Andreas J. Reichel
2019-02-27 16:12 ` Henning Schild
2019-03-01 9:09 ` Andreas Reichel
2019-03-01 10:18 ` Henning Schild
2019-03-06 16:29 ` Andreas Reichel
2019-03-01 9:16 ` Andreas Reichel
2019-03-01 10:11 ` Henning Schild
2019-03-01 10:22 ` Henning Schild
2019-03-06 16:29 ` Andreas Reichel
2019-02-27 15:18 ` [PATCH v2 2/3] Use all source lists in target root apt Andreas J. Reichel
2019-02-27 15:18 ` [PATCH v2 3/3] Separate apt-key entries from default keyring Andreas J. Reichel
2019-02-27 16:14 ` Henning Schild [this message]
2019-03-01 9:08 ` Andreas Reichel
2019-02-27 16:15 ` [PATCH v2 0/3] Fixes usage of additional apt keys Henning Schild
2019-03-01 9:17 ` Andreas Reichel
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=20190227171443.7bb07fc2@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=andreas.reichel.ext@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