From: "Amy_Fong@mentor.com" <amy.fong.3142@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: base-apt signing interface could be improved
Date: Thu, 13 Jun 2019 09:55:29 -0700 (PDT) [thread overview]
Message-ID: <e8d1cf1d-4cd8-4eb8-b695-3bed3d97e27f@googlegroups.com> (raw)
In-Reply-To: <20190606154558.7eea07bd@md1za8fc.ad001.siemens.net>
[-- Attachment #1.1: Type: text/plain, Size: 2745 bytes --]
On Thursday, 6 June 2019 09:46:02 UTC-4, Henning Schild wrote:
>
> Hi,
>
> i just had a quick look at the implementation of the base-apt signing
> for the first time. The interface is not ideal and has potential for
> the signing key and the checking key not actually belonging together.
>
> As far as i understand the code i read, Isar will start signing
> base-apt if BASE_REPO_KEY is set to anything. The private key it will
> use to sign the repo is not specified at all, it will be whatever gnupg
> defaults to, given its configuration.
>
> I would suggest to switch from "SignWith yes" to "SignWith <keyid>",
> and derive the id from BASE_REPO_KEY.
>
> Further improvements would be to actually configure gnupg inside Isar
> and not rely on an outside configuration. Relying on the outside config
> means that all (multi)configs will have to use the same keypair.
> So we would add
>
> BASE_REPO_KEY_PRIVATE and ..._PASSPHRASE
>
> Now we would create a new gpg homedir next to where we store base-apt.
> We would import that one key there and potentially unlock it with its
> passphrase. If we clean and rebuild we get a working gpghome for sure.
>
> Henning
>
Hi,
Perhaps something like the following ...
Of course, since BASE_REPO_KEY permits specifying
multiple keys, this raises a question of which keyid?
Amy
>From 5ceb4a2ef97bc7fa6c44cd9ce6f73f9a831773f3 Mon Sep 17 00:00:00 2001
From: Amy Fong <Amy_Fong@mentor.com>
Date: Thu, 13 Jun 2019 12:52:06 -0400
Subject: [PATCH] base-apt: Use BASE_REPO_KEY for signing
Extract keyid from BASE_REPO_KEY for signing
Signed-off-by: Amy Fong <Amy_Fong@mentor.com>
---
meta/recipes-devtools/base-apt/base-apt.bb | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/base-apt/base-apt.bb
b/meta/recipes-devtools/base-apt/base-apt.bb
index 1c0b4c6..81245f7 100644
--- a/meta/recipes-devtools/base-apt/base-apt.bb
+++ b/meta/recipes-devtools/base-apt/base-apt.bb
@@ -19,8 +19,15 @@ do_cache_config() {
sed -e "s#{CODENAME}#"${BASE_DISTRO_CODENAME}"#g" \
${WORKDIR}/distributions.in > ${CACHE_CONF_DIR}/distributions
if [ "${BASE_REPO_KEY}" ] ; then
+ option="yes"
+ for key in ${BASE_REPO_KEY}; do
+ keyid=$(wget -qO - $key | gpg --keyid-format 0xlong
--with-colons - 2>/dev/null |grep "^pub:" |awk -F':' '{print $5;}')
+ if [ -n "$keyid" ]; then
+ option="$keyid"
+ fi
+ done
# To generate Release.gpg
- echo "SignWith: yes" >> ${CACHE_CONF_DIR}/distributions
+ echo "SignWith: $option" >> ${CACHE_CONF_DIR}/distributions
fi
fi
--
2.20.1
[-- Attachment #1.2: Type: text/html, Size: 3671 bytes --]
next prev parent reply other threads:[~2019-06-13 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 13:45 Henning Schild
2019-06-13 16:55 ` Amy_Fong@mentor.com [this message]
2019-06-14 8:22 ` Henning Schild
2019-06-14 13:50 ` Amy_Fong@mentor.com
2019-06-17 11:19 ` Henning Schild
2019-06-17 11:36 ` Claudius Heine
2019-06-28 6:30 ` vijaikumar.kanagarajan
2019-06-28 8:14 ` Henning Schild
2019-07-24 8:47 ` Vijai Kumar K
2019-06-27 17:04 ` vijaikumar.kanagarajan
2019-06-28 8:04 ` Henning Schild
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=e8d1cf1d-4cd8-4eb8-b695-3bed3d97e27f@googlegroups.com \
--to=amy.fong.3142@gmail.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