From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Release Signatures
Date: Mon, 06 Dec 2021 09:22:35 +0100 [thread overview]
Message-ID: <1638778547.sda2qoj11l.astroid@nora.none> (raw)
In-Reply-To: <27cd3cf9-eb19-44a3-b1bc-2d2e302181b6@www.fastmail.com>
On December 5, 2021 6:42 pm, Sid Spry wrote:
> Are checksums and release signatures available for install media?
yes.
checksum via TLS:
https://proxmox.com/en/downloads/item/proxmox-ve-7-1-iso-installer
(applies to other products/versions as well)
checksum + signature:
http://download.proxmox.com/iso/
signing key == repository key[1,2,3]
1: checksum via TLS https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye#Adapt_your_sources.list
2: keys via TLS https://git.proxmox.com/?p=proxmox-archive-keyring.git;a=tree;f=debian;h=d3538cb8ad0753a45ded226c56e1ac0323a83588;hb=HEAD
3: or installed on any current PVE/PMG/PBS system via
`proxmox-archive-keyring` ;)
> What about code signing on repos?
no, there is no signing of git commits/.. . our consumable artifacts for
users are deb packages, which are chained to the repo signing key as
trust anchor.
prev parent reply other threads:[~2021-12-06 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 17:42 Sid Spry
2021-12-06 8:22 ` Fabian Grünbichler [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=1638778547.sda2qoj11l.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-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