From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Shannon Sterz" <s.sterz@proxmox.com>, <pdm-devel@lists.proxmox.com>
Subject: Re: [PATCH datacenter-manager/proxmox{,-backup} 00/11] TLS Certificate Rotation
Date: Thu, 30 Jul 2026 15:33:09 +0200 [thread overview]
Message-ID: <DKBXZX3ZL5I5.3U3FNXU5W9NU1@proxmox.com> (raw)
In-Reply-To: <20260618115443.48618-1-s.sterz@proxmox.com>
Superseded-by: https://lore.proxmox.com/pbs-devel/20260730133158.418015-1-s.sterz@proxmox.com/
On Thu Jun 18, 2026 at 1:54 PM CEST, Shannon Sterz wrote:
> this series adds certificate rotation to Proxmox Backup Server and Proxmox
> Datacenter Manager. currently, both products issue a certificate that is valid
> for almost 1000 years (365000 days). no cryptographic key can reasonably be
> considered secure for this amount of time. this series:
>
> - allows specifying the lifetime of the certificate when creating one via
> proxmox-acme-api and reduces the default to 3650 days (almost ten years).
> - sends and logs reminders 30 days before a certificate expires (pdm currently
> does not support the notification framework yet, so adding notifications is
> left as future work here).
> - refreshes a certificate at the earliest 15 days before it expires, logs
> and notifies when that happens.
> - warns on certificates with excessive lifetimes (>3650 days) and documents
> how to manually update them.
> - for pdm: exposes cert handling cli methods in proxmox-datacenter-manager-admin.
> - fixes up some inconsistencies in the ui and docs in regards to pdm's
> certificate location.
>
> ## Testing
>
> the easiest way to test this is to manipulate the date of the host with `date
> --set` and then manually trigger the daily update binary for each product:
>
> * PBS: `/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-daily-update`
> * PDM: `/usr/libexec/proxmox/proxmox-datacenter-manager-daily-update`
>
> you can then check the logs and the certificate itself to see what happened.
> specifying the `PBS_LOG` environment variable with the parameter `trace` or
> `debug` will also enable debug logging here.
>
> ## Open Questions
>
> + 10 years is still a long time and i'd rather reduce that further down if
> possible. see the first patch for proxmox-acme-api for more info.
> + should we remove pre-existing long lasting certificates by ourselves? imo
> that is too risky at the moment given that an unplanned certificate rotation
> could cause backups to fail.
> + notifying every day for 15 days before the renewal might be excessive, see
> the second commit for pbs.
>
> ## Future Work
>
> - pve and pdm should be extended to allow automatically updating allowed
> fingerprints before a new self-signed certificate goes into action. a series
> demonstrating this for pve<->pdm has already been sent [1]. if this series gets
> approved, i'll happily adapt the mechanism for pbs<->pve.
> - pdm should send notifications similar to pbs once support for notifications
> is added.
>
> ## Changelog
>
> * v1: https://lore.proxmox.com/pbs-devel/20260422124022.17952-1-s.sterz@proxmox.com/
>
> changes since v1:
>
> + dropped a patch for proxmox-yew-comp that got applied already
> + rebased on current master for all three repos
>
> * rfc: https://lore.proxmox.com/pbs-devel/20260407135714.490747-1-s.sterz@proxmox.com/
>
> changes since rfc:
>
> + add patches that avoid hard-coding the certificate file name in yew-comp
> and use the proper filename in pdm
> + update pdm renewal docs patch to avoid confusion
> + re-base on current master
>
> [1]: https://lore.proxmox.com/pdm-devel/20260611120327.257523-1-s.sterz@proxmox.com/
>
>
> proxmox:
>
> Shannon Sterz (1):
> acme-api: make self-signed certificate expiry configurable
>
> proxmox-acme-api/src/certificate_helpers.rs | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>
> backup:
>
> Shannon Sterz (5):
> config: use proxmox_acme_api for generating self-signed certificates
> config: adapt to api change in proxmox_acme_api, add expiry paramter
> config/server/api: add certificate renewal logic including
> notifications
> daily-update/docs: warn on excessive self-signed certificate lifetime
> backup-manager cli: `cert update` can create auth and csrf key
>
> debian/proxmox-backup-server.install | 4 +
> docs/certificate-management.rst | 31 ++++++
> src/api2/node/certificates.rs | 44 +++++++++
> src/bin/proxmox-daily-update.rs | 32 +++++++
> src/bin/proxmox_backup_manager/cert.rs | 2 +
> src/config/mod.rs | 96 ++-----------------
> src/server/notifications/mod.rs | 50 ++++++++++
> templates/Makefile | 66 +++++++------
> templates/default/cert-refresh-body.txt.hbs | 8 ++
> .../default/cert-refresh-subject.txt.hbs | 1 +
> .../cert-upcoming-refresh-body.txt.hbs | 9 ++
> .../cert-upcoming-refresh-subject.txt.hbs | 1 +
> 12 files changed, 227 insertions(+), 117 deletions(-)
> create mode 100644 templates/default/cert-refresh-body.txt.hbs
> create mode 100644 templates/default/cert-refresh-subject.txt.hbs
> create mode 100644 templates/default/cert-upcoming-refresh-body.txt.hbs
> create mode 100644 templates/default/cert-upcoming-refresh-subject.txt.hbs
>
>
> datacenter-manager:
>
> Shannon Sterz (5):
> certs: adapt to api change in proxmox_acme_api, add expiry paramter
> api/auth/bin: add certificate renewal logic
> cli: expose certificate management endpoints via the cli
> daily-update/docs: warn on excessive tls certificate validity periods
> docs/certificates: use correct certificate file name
>
> cli/admin/Cargo.toml | 2 +
> cli/admin/src/cert.rs | 86 +++++++++++++++++++
> cli/admin/src/main.rs | 2 +
> docs/certificate-management.rst | 32 +++++++
> server/Cargo.toml | 1 +
> server/src/api/nodes/certificates.rs | 50 ++++++++++-
> server/src/auth/certs.rs | 4 +-
> ...proxmox-datacenter-manager-daily-update.rs | 30 +++++++
> 8 files changed, 205 insertions(+), 2 deletions(-)
> create mode 100644 cli/admin/src/cert.rs
>
>
> Summary over all repositories:
> 21 files changed, 434 insertions(+), 120 deletions(-)
prev parent reply other threads:[~2026-07-30 13:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 11:54 [PATCH datacenter-manager/proxmox{,-backup} 00/11] TLS Certificate Rotation Shannon Sterz
2026-06-18 11:54 ` [PATCH proxmox 01/11] acme-api: make self-signed certificate expiry configurable Shannon Sterz
2026-07-10 11:15 ` Lukas Wagner
2026-07-29 9:53 ` Shannon Sterz
2026-06-18 11:54 ` [PATCH proxmox-backup 02/11] config: use proxmox_acme_api for generating self-signed certificates Shannon Sterz
2026-06-18 11:54 ` [PATCH proxmox-backup 03/11] config: adapt to api change in proxmox_acme_api, add expiry paramter Shannon Sterz
2026-06-18 11:54 ` [PATCH proxmox-backup 04/11] config/server/api: add certificate renewal logic including notifications Shannon Sterz
2026-07-10 11:17 ` Lukas Wagner
2026-07-29 9:53 ` Shannon Sterz
2026-07-29 10:08 ` Lukas Wagner
2026-07-29 10:13 ` Shannon Sterz
2026-07-29 10:29 ` Lukas Wagner
2026-06-18 11:54 ` [PATCH proxmox-backup 05/11] daily-update/docs: warn on excessive self-signed certificate lifetime Shannon Sterz
2026-07-10 11:17 ` Lukas Wagner
2026-07-29 9:53 ` Shannon Sterz
2026-06-18 11:54 ` [PATCH proxmox-backup 06/11] backup-manager cli: `cert update` can create auth and csrf key Shannon Sterz
2026-06-18 11:54 ` [PATCH datacenter-manager 07/11] certs: adapt to api change in proxmox_acme_api, add expiry paramter Shannon Sterz
2026-06-18 11:54 ` [PATCH datacenter-manager 08/11] api/auth/bin: add certificate renewal logic Shannon Sterz
2026-07-10 11:17 ` Lukas Wagner
2026-07-29 9:53 ` Shannon Sterz
2026-06-18 11:54 ` [PATCH datacenter-manager 09/11] cli: expose certificate management endpoints via the cli Shannon Sterz
2026-06-18 11:54 ` [PATCH datacenter-manager 10/11] daily-update/docs: warn on excessive tls certificate validity periods Shannon Sterz
2026-06-18 11:54 ` [PATCH datacenter-manager 11/11] docs/certificates: use correct certificate file name Shannon Sterz
2026-07-30 13:33 ` Shannon Sterz [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=DKBXZX3ZL5I5.3U3FNXU5W9NU1@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pdm-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.