From: Shannon Sterz <s.sterz@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup] docs: update apt key installation guide to use the new release key rings
Date: Fri, 18 Jul 2025 11:14:52 +0200 [thread overview]
Message-ID: <20250718091452.69458-1-s.sterz@proxmox.com> (raw)
Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
---
docs/package-repositories.rst | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/docs/package-repositories.rst b/docs/package-repositories.rst
index afae39c8..90853784 100644
--- a/docs/package-repositories.rst
+++ b/docs/package-repositories.rst
@@ -242,21 +242,29 @@ key with the following commands:
.. code-block:: console
- # wget https://enterprise.proxmox.com/debian/proxmox-release-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpg
+ # wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpg
-Verify the SHA512 checksum afterwards with the expected output below:
+.. note:: The `wget` command above adds the keyring for Proxmox releases based
+ on Debian Trixie. Once the `proxmox-archive-keyring` package is installed,
+ it will manage this file. At that point, the hashes below may no longer
+ match the hashes of this file, as keys for new Proxmox releases get added or
+ removed. This is intended, `apt` will ensure that only trusted keys are
+ being used. **Modifying this file is discouraged once
+ `proxmox-archive-keyring` is installed.**
+
+Verify the SHA256 checksum afterwards with the expected output below:
.. code-block:: console
- # sha512sum /usr/share/keyrings/proxmox-archive-keyring.gpg
- 8678f2327c49276615288d7ca11e7d296bc8a2b96946fe565a9c81e533f9b15a5dbbad210a0ad5cd46d361ff1d3c4bac55844bc296beefa4f88b86e44e69fa51 /usr/share/keyrings/proxmox-archive-keyring.gpg
+ # sha256sum /usr/share/keyrings/proxmox-archive-keyring.gpg
+ 136673be77aba35dcce385b28737689ad64fd785a797e57897589aed08db6e45 /usr/share/keyrings/proxmox-archive-keyring.gpg
and the md5sum, with the expected output below:
.. code-block:: console
# md5sum /usr/share/keyrings/proxmox-archive-keyring.gpg
- c94e3775fbafec13fec20f981db61e93 /usr/share/keyrings/proxmox-archive-keyring.gpg
+ 77c8b1166d15ce8350102ab1bca2fcbf /usr/share/keyrings/proxmox-archive-keyring.gpg
.. note:: Make sure that the path that you download the key to, matches the
path specified in the ``Signed-By:`` lines in your repository stanzas from
--
2.39.5
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next reply other threads:[~2025-07-18 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 9:14 Shannon Sterz [this message]
2025-08-28 7:35 ` Shannon Sterz
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=20250718091452.69458-1-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pbs-devel@lists.proxmox.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