From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: applied-series: [pve-devel] [PATCH proxmox v8 0/5] fix #5207: apt: check signature of repos with proxmox-pgp
Date: Thu, 26 Feb 2026 12:15:01 +0100 [thread overview]
Message-ID: <1a15c9a2-5789-4341-8212-ce781ad3718c@proxmox.com> (raw)
In-Reply-To: <177203312136.3390599.4447093998607966654@yuna.proxmox.com>
On 2/25/26 4:25 PM, Fabian Grünbichler wrote:
> Quoting Nicolas Frey (2026-01-14 10:35:57)
>> This patch series moves in pgp verification code from POM into its
>> own micro-crate `proxmox-pgp` to reuse it to verify a package is of
>> Proxmox Origin, which fixes #5207.
>>
>> If this patch series is applied, then `proxmox-offline-mirror` should
>> use the `proxmox-pgp` crate.
>
> could you send patches for that as well? :)
>
Sent: https://lore.proxmox.com/pve-devel/20260226111239.80602-1-n.frey@proxmox.com/T/#t
prev parent reply other threads:[~2026-02-26 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 9:35 Nicolas Frey
2026-01-14 9:35 ` [pve-devel] [PATCH proxmox v8 1/5] add proxmox-pgp subcrate, move POM verifier code to it Nicolas Frey
2026-01-14 9:35 ` [pve-devel] [PATCH proxmox v8 2/5] proxmox-pgp: add unit tests for {de, at}tached signatures Nicolas Frey
2026-01-14 9:36 ` [pve-devel] [PATCH proxmox v8 3/5] fix #5207: apt: check signature of repos with proxmox-pgp Nicolas Frey
2026-01-14 9:36 ` [pve-devel] [PATCH proxmox v8 4/5] apt: add tests for POM release filenames Nicolas Frey
2026-01-14 9:36 ` [pve-devel] [PATCH proxmox v8 5/5] apt: check for local POM InRelease as fallback Nicolas Frey
2026-02-25 15:25 ` applied-series: [pve-devel] [PATCH proxmox v8 0/5] fix #5207: apt: check signature of repos with proxmox-pgp Fabian Grünbichler
2026-02-26 11:15 ` Nicolas Frey [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=1a15c9a2-5789-4341-8212-ce781ad3718c@proxmox.com \
--to=n.frey@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