From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] meta: Update expired debian ports signing key
Date: Thu, 03 Feb 2022 16:50:46 +0300 [thread overview]
Message-ID: <2121626.hkbZ0PkbqX@home> (raw)
In-Reply-To: <20220203100256.30893-1-ubely@ilbers.de>
In the email from Thursday, 3 February 2022 13:02:56 +03 user Uladzimir Bely
wrote:
> Replace expired Debian Ports Archive Automatic Signing Key (2021)
> (ID:5A88D659DCB811BB) by new Debian Ports Archive Automatic Signing Key
> (2022) (ID: E852514F5DF312F6) to make debian-sid-ports targets work.
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> meta/conf/distro/debian-sid-ports.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/distro/debian-sid-ports.conf
> b/meta/conf/distro/debian-sid-ports.conf index 32bd32f3..c8d70750 100644
> --- a/meta/conf/distro/debian-sid-ports.conf
> +++ b/meta/conf/distro/debian-sid-ports.conf
> @@ -10,7 +10,7 @@ BASE_DISTRO_CODENAME = "sid"
>
> HOST_DISTRO ?= "debian-sid"
>
> -DEBIAN_PORTS_KEY =
> "https://www.ports.debian.org/archive_2021.key;sha256sum=44a0c59cac5385cd0a
> 1506f695fbd2381fb71a04d8afc05248ad00a0ec6052aa" +DEBIAN_PORTS_KEY =
> "https://www.ports.debian.org/archive_2022.key;sha256sum=213531906f80d79a5d
> bc8573f57f2a2831b71383cc2d568feba97bb4db94adcc"
>
> DISTRO_APT_SOURCES =
> "conf/distro/debian-${BASE_DISTRO_CODENAME}-ports.list"
> DISTRO_BOOTSTRAP_KEYS += "${DEBIAN_PORTS_KEY}"
Some investigations:
It seems, they update keys every year. Currently, archive_2022.key is used for
signing (valid from Feb 2022 till Jan 2023). But, at the same time,
archive_2023.key (created about month ago) is available, and they start using
it to sign releases on Feb. 2023.
So, we could keep 2 keys in conf file - one that works now, another that will
work next year. So, next time we won't face the problem with debootstrapping
again, of course providing we do these key updates once a year.
--
Uladzimir Bely
prev parent reply other threads:[~2022-02-03 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 10:02 Uladzimir Bely
2022-02-03 13:50 ` Uladzimir Bely [this message]
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=2121626.hkbZ0PkbqX@home \
--to=ubely@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