]> git.proxmox.com Git - pmg-api.git/commit
projects / pmg-api.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5d30f58) | patch
cluster: use old and new fingerprint on master
authorStoiko Ivanov <s.ivanov@proxmox.com>
Thu, 18 Mar 2021 15:14:48 +0000 (16:14 +0100)
committerThomas Lamprecht <t.lamprecht@proxmox.com>
Thu, 18 Mar 2021 15:31:46 +0000 (16:31 +0100)
commit0b0c58e6ee1d25e6dd74daa4dff1f0ddc3eb6d84
treeb04cdb0926602ea0a1e81d207d5e740467efa51dtree
parent5d30f58689282b84b9df177b1c295fbb4aac9656commit | diff
cluster: use old and new fingerprint on master

when triggering a fingerprint update on master right after reloading
pmgproxy as we do for ACME certificates it can happen that the
connection is made against the old pmgproxy process (with the old
fingerprint). Simply trusting both fingerprints in that case seems
acceptable from a security perspective and makes the fingerprint
update more robust

Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
src/PMG/Cluster.pm diff | blob | blame | history
PMG API