From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id AEE251FF191 for ; Tue, 22 Jul 2025 16:26:43 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D310EBA1D; Tue, 22 Jul 2025 16:27:56 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Shannon Sterz Date: Tue, 22 Jul 2025 16:27:37 +0200 Message-ID: <175319445313.1663032.7708558670562730338.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250722123658.196232-1-s.sterz@proxmox.com> References: <20250722123658.196232-1-s.sterz@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753194463439 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [PATCH manager 1/2] fix #6539: apl: use sqv instead of gpgv to verify signatures X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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