From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox v3 02/16] tls-certificates: add days_valid parameter to create_self_signed_cert
Date: Thu, 06 Aug 2026 15:49:49 +0200 [thread overview]
Message-ID: <DKHWQHROLZLH.3KEXQAPIGXLFR@proxmox.com> (raw)
In-Reply-To: <1786021372.xnuxft8ug6.astroid@yuna.none>
On Thu Aug 6, 2026 at 3:09 PM CEST, Fabian Grünbichler wrote:
> On August 5, 2026 5:52 pm, Shannon Sterz wrote:
>> to allow specifying how long a certificate should be valid for. also
>> adds unit tests to verify this behavior.
>>
>> Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
>> ---
>>
>> Notes:
>> imo, we could go down even more. as far as i am aware there is no real
>> limit that is being enforced here for self-signed certificates from a
>> browser perspective. they are already trusted on an exemption-basis
>> anyway. however, certificates signed by public CAs will only be valid
>> for a maximum of 47 days by 2029 [1].
>>
>> hence, i would personally either adopt the same limit or go down to a
>> year, as a sensible middle-ground. certificate rotation should really
>> be automated even in self-signed scenarios. we also had cases in the
>> past, where customers already ran into an issue because they wanted to
>> limit the lifetime of their certificates below 30 days [2]. meaning
>> that there is a need out there for shorter-lived certificates (though,
>> in that case a custom CA & ACME setup was used).
>
> the main issue with decreasing the lifetime of the certificate is that
> for PBS in particular, it needs to be pinned in potentially a lot of
> places (that might not access the PBS system very often).
>
> so IMHO the order of application needs to be:
> - this series with a lifetime roughly matching a deployment of a PBS
> system
> - implement staging support on the PBS server-side, and all clients
> (PBS, PVE, PDM)
> - wait (for clients to upgrade, including some time for external clients
> to adapt as well
> - reduce lifetime to a year (and maybe warning threshold for getting rid
> of old, long-lived certificates)
completely agree. imo 10 years is a reasonable time frame for this. that
would 5 pbs releases or so. imo we can do the first three steps outlined
here before pbs 5 drops and the decrease the lifetime with pbs 6 or 7.
that should give enough time for everyone to adjust hopefully.
if really required, users could still get a custom long-lived cert and
use that instead.
-->8 snip 8<--
next prev parent reply other threads:[~2026-08-06 13:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 15:52 [PATCH datacenter-manager/proxmox{,-backup} v3 00/16] TLS Certificate Rotation Shannon Sterz
2026-08-05 15:52 ` [PATCH proxmox v3 01/16] acme-api/tls-certificates: add new crate collecting tls related helpers Shannon Sterz
2026-08-05 15:52 ` [PATCH proxmox v3 02/16] tls-certificates: add days_valid parameter to create_self_signed_cert Shannon Sterz
2026-08-06 13:09 ` Fabian Grünbichler
2026-08-06 13:49 ` Shannon Sterz [this message]
2026-08-05 15:52 ` [PATCH proxmox v3 03/16] tls-certificates: add self_signed_cert_expires_in to check certificates Shannon Sterz
2026-08-06 13:09 ` Fabian Grünbichler
2026-08-06 13:49 ` Fabian Grünbichler
2026-08-05 15:52 ` [PATCH proxmox v3 04/16] acme-api: stop re-exporting create_self_signed_cert Shannon Sterz
2026-08-05 15:52 ` [PATCH proxmox-backup v3 05/16] config: use proxmox_tls_certificates for generating self-signed certificates Shannon Sterz
2026-08-06 13:09 ` Fabian Grünbichler
2026-08-06 13:49 ` Shannon Sterz
2026-08-05 15:52 ` [PATCH proxmox-backup v3 06/16] config/server/api: add certificate renewal logic including notifications Shannon Sterz
2026-08-06 13:09 ` Fabian Grünbichler
2026-08-05 15:53 ` [PATCH proxmox-backup v3 07/16] daily update: warn about excessive self-signed certificate lifetime Shannon Sterz
2026-08-05 15:53 ` [PATCH proxmox-backup v3 08/16] docs: document force refreshing long-lived certificates Shannon Sterz
2026-08-05 15:53 ` [PATCH proxmox-backup v3 09/16] backup-manager cli: `cert update` can create auth and csrf key Shannon Sterz
2026-08-06 13:27 ` applied: " Fabian Grünbichler
2026-08-05 15:53 ` [PATCH proxmox-backup v3 10/16] notifications: use `Severity::Error` for acme renewal failures Shannon Sterz
2026-08-06 13:27 ` applied: " Fabian Grünbichler
2026-08-05 15:53 ` [PATCH datacenter-manager v3 11/16] certs: use proxmox-tls-certificates directly, add days_valid parameter Shannon Sterz
2026-08-05 15:53 ` [PATCH datacenter-manager v3 12/16] api/auth/bin: add certificate renewal logic Shannon Sterz
2026-08-05 15:53 ` [PATCH datacenter-manager v3 13/16] cli: expose certificate management endpoints via the cli Shannon Sterz
2026-08-06 13:53 ` applied: " Fabian Grünbichler
2026-08-05 15:53 ` [PATCH datacenter-manager v3 14/16] daily-update: warn about certificates with excessive lifetimes Shannon Sterz
2026-08-05 15:53 ` [PATCH datacenter-manager v3 15/16] docs: add section on forcing a new self-signed certificate Shannon Sterz
2026-08-05 15:53 ` [PATCH datacenter-manager v3 16/16] docs/certificates: use correct certificate file name Shannon Sterz
2026-08-06 13:54 ` partially-applied: " Fabian Grünbichler
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=DKHWQHROLZLH.3KEXQAPIGXLFR@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pbs-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.