From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied: [PATCH proxmox-backup 1/1] sync: pull: refuse to overwrite pre-existing encrypted snapshot
Date: Wed, 29 Apr 2026 18:23:50 +0200 [thread overview]
Message-ID: <177747982929.3682415.16295676132262746651.b4-ty@b4> (raw)
In-Reply-To: <20260429143740.886870-1-c.ebner@proxmox.com>
On Wed, 29 Apr 2026 16:37:40 +0200, Christian Ebner wrote:
> If the source snapshot is not encrypted, the target snapshot however
> is pre-existing and there is no decryption key which would detect the
> mismatch, the unencrypted source will overwrite the encrypted target
> due to resync because of mismatching raw manifests.
>
> Further, currently regular syncs of two potentially clashing
> snapshots from different sources would lead to overwritig of the
> target snapshot as well, since byte wise manifests differ.
>
> [...]
Applied, thanks!
[1/1] sync: pull: refuse to overwrite pre-existing encrypted snapshot
commit: acfd017b761339177e5b069695fd3737178641f9
prev parent reply other threads:[~2026-04-29 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 14:37 [PATCH proxmox-backup 1/1] sync: pull: refuse to overwrite pre-existing encrypted snapshot Christian Ebner
2026-04-29 16:23 ` Thomas Lamprecht [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=177747982929.3682415.16295676132262746651.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox