From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Shannon Sterz <s.sterz@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager 1/2] fix #6539: apl: use sqv instead of gpgv to verify signatures
Date: Tue, 22 Jul 2025 16:27:37 +0200 [thread overview]
Message-ID: <175319445313.1663032.7708558670562730338.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250722123658.196232-1-s.sterz@proxmox.com>
On Tue, 22 Jul 2025 14:36:57 +0200, Shannon Sterz wrote:
> debian trixie based installs don't ship with gpgv so take this
> opportunity and use sqv directly. sqv can deal with both armored and
> dearmored keys. this has the side-effect of closing #6539. which
> occured, due to sequioa dropping the `--binary` option for merging
> keys into a keyring and would always output them in an armored
> formart. gpgv cannot handle armored keys and would therefore fail to
> verify signatures.
>
> [...]
Applied, thanks!
[1/2] fix #6539: apl: use sqv instead of gpgv to verify signatures
commit: 15a67b13e7e9b1c06f473fdc62b96f983293e063
[2/2] apl: make keyring generation output keys as binary again
commit: 5034a93f6d6ede028ba53b8a2963a882ba0bafa3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-22 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 12:36 [pve-devel] " Shannon Sterz
2025-07-22 12:36 ` [pve-devel] [PATCH manager 2/2] apl: make keyring generation output keys as binary again Shannon Sterz
2025-07-22 14:27 ` Thomas Lamprecht [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=175319445313.1663032.7708558670562730338.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@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