From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 3/3] doc/user_manual: Describe gpg signing of local repo
Date: Mon, 4 Feb 2019 19:54:20 +0000 [thread overview]
Message-ID: <20190204195420.7972-4-mosipov@ilbers.de> (raw)
In-Reply-To: <20190204195420.7972-1-mosipov@ilbers.de>
Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
---
doc/user_manual.md | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index eebcaa9..c9c40ae 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -727,6 +727,12 @@ Cache upstream debian packages to reduce time for further downloads and to be ab
- Trigger creation of local apt caching Debian packages during image generation.
+Note: By default the local caching repo is not gpg signed.
+If you want to sign it, `gpg` has to be installed in your host system and
+a default key pair is generated,
+set `BASE_REPO_KEY` in `conf/local.conf` to `SRC_URI` of your public key,
+f.e. 'BASE_REPO_KEY = "file://<absolute_path_to_your_pub_key_file>"'.
+
```
bitbake -c cache_base_repo multiconfig:qemuarm-stretch:isar-image-base
```
@@ -749,7 +755,3 @@ sudo rm -rf tmp
```
bitbake multiconfig:qemuarm-stretch:isar-image-base
```
-
-### Limitation
-
-So far the local base-apt repo is not gpg signed.
--
2.11.0
next prev parent reply other threads:[~2019-02-04 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 19:54 [PATCH 0/3] Signing local cache repo Maxim Yu. Osipov
2019-02-04 19:54 ` [PATCH 1/3] isar-bootstrap: Allow to set local keys in DISTRO_APT_KEYS Maxim Yu. Osipov
2019-02-04 19:54 ` [PATCH 2/3] base-apt: Introduce BASE_REPO_KEY to sign local repo Maxim Yu. Osipov
2019-02-04 19:54 ` Maxim Yu. Osipov [this message]
2019-02-08 14:32 ` [PATCH 0/3] Signing local cache repo Maxim Yu. Osipov
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=20190204195420.7972-4-mosipov@ilbers.de \
--to=mosipov@ilbers.de \
--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