From: Roland Kammerer <roland.kammerer@linbit.com>
To: drbd-announce@lists.linbit.com, drbd-user@lists.linbit.com
Subject: linbit-keyring
Date: Fri, 25 Oct 2024 12:47:19 +0200 [thread overview]
Message-ID: <Zxt3N5qWG6DI9PED@arm64> (raw)
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Dear DRBD users,
this is meant for our customers as well as FLOSS users that use any of
our public repos (except the Ubuntu PPA).
The short version: There is now a linbit-keyring package with our old
key and our new key and we will start using the new one on November the
15th to sign repo meta data. As the keyring contains both keys you can
install that package now and change your repo config (if necessary),
then you don't even notice the upcoming changes.
Details are described here[1], if there are any questions, please ask.
[1] https://kb.linbit.com/linbit-keyring-software-package
Regards, rck
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-10-25 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 10:47 Roland Kammerer [this message]
2024-11-21 11:12 ` linbit-keyring, new LINBIT Package and Repository Signing Key Lars Ellenberg
2024-11-21 11:47 ` Roland Kammerer
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=Zxt3N5qWG6DI9PED@arm64 \
--to=roland.kammerer@linbit.com \
--cc=drbd-announce@lists.linbit.com \
--cc=drbd-user@lists.linbit.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