From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 220EF1FF13F for ; Thu, 23 Apr 2026 20:58:34 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F41FAD98; Thu, 23 Apr 2026 20:58:33 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Manuel Federanko Subject: applied: [PATCH proxmox-backup] acme: partially fix #6372: scale certificate renewal checks by lifetime Date: Thu, 23 Apr 2026 20:57:59 +0200 Message-ID: <177697067688.114614.5634527097442157999.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260421144645.275884-1-m.federanko@proxmox.com> References: <20260421144645.275884-1-m.federanko@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776970620648 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.002 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: SAU3M3EVBPWRK3NSRWVUFBCMNB3G6UWG X-Message-ID-Hash: SAU3M3EVBPWRK3NSRWVUFBCMNB3G6UWG X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 21 Apr 2026 16:46:45 +0200, Manuel Federanko wrote: > Start renewing a certificate once 2/3 of its total lifetime have passed, > instead of the hardcoded 30 days. This stays consistent with many > certificates, which are valid for 90 days. > > The update service runs daily, impose a 3 day minimum remaining lifetime > to still be able to handle transient failures for certificate renewals. > > [...] Applied with a small set of mostly cosmetic follow-ups on top, thanks! [1/1] acme: partially fix #6372: scale certificate renewal checks by lifetime commit: 29bd6b89ca3b3d33e89bd0277daf46b39b210273