all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox-backup 0/2] gracefully handle signature mismatch from previous manifest load during encrypting push sync
Date: Wed, 29 Apr 2026 11:28:45 +0200	[thread overview]
Message-ID: <20260429092847.381438-1-c.ebner@proxmox.com> (raw)

This patches more gracefully handle an otherwise rather alerting log
message during push sync jobs with configured active encryption key,
stating a key mismatch in the manifest signature check error.

During push, the previous snapshot of the backup group on the remote
target is being used for chunk deduplicaton on upload. When fetching,
the previous manifest's signature is checked against the backup
writer's key, which may however not match if the previous snapshot is
encrypted by a different key.
This being normal operation, log a less alerting log message stating
that deduplication using the previous snapshot is skipped instead.

Christian Ebner (2):
  client: allow skipping signature check on previous manifest fetching
  sync: push: gracefully handle previous manifest signature mismatches

 pbs-client/src/backup_writer.rs | 22 +++++++++++++++++++---
 src/server/push.rs              | 24 ++++++++++++++++++++++--
 2 files changed, 41 insertions(+), 5 deletions(-)

-- 
2.47.3





             reply	other threads:[~2026-04-29  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29  9:28 Christian Ebner [this message]
2026-04-29  9:28 ` [PATCH proxmox-backup 1/2] client: allow skipping signature check on previous manifest fetching Christian Ebner
2026-04-29 11:43   ` Fabian Grünbichler
2026-04-29 11:52     ` Christian Ebner
2026-04-29  9:28 ` [PATCH proxmox-backup 2/2] sync: push: gracefully handle previous manifest signature mismatches Christian Ebner
2026-04-29 11:43   ` 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=20260429092847.381438-1-c.ebner@proxmox.com \
    --to=c.ebner@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal