From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied-series: [PATCH proxmox-backup v3 0/5] restrict previous manifest reuse checks for push sync jobs
Date: Wed, 29 Jul 2026 15:00:58 +0200 [thread overview]
Message-ID: <178533005540.644993.6938528626229983453.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260729090737.135385-1-c.ebner@proxmox.com>
On Wed, 29 Jul 2026 11:07:32 +0200, Christian Ebner wrote:
> Restrict and rework the checks for reuse of previous snapshots
> manifest's for push sync jobs, in particular with key and signature
> mismatches for sync jobs with active encryption key.
> In particular, only allow reuse of the previous manifest if either
> the previous manifest is not encrypted, and the push sync will also
> not encrypt or the previous manifest is encrypted with the matching
> active encryption key configured for the sync job, the manifest's
> signature being verified with that key.
>
> [...]
Applied, thanks!
[1/5] datastore: data blob: refactor crypt mode method
commit: b00fe46ee37479805bebff0eb3e2b131ca88c9b1
[2/5] datastore: data blob: refactor decoding method
commit: 71ab92143a2e98a2bd9f4756f1e860348f1a72af
[3/5] client: backup writer: pass no crypt config to manifest blob decoder
commit: 0f60e71d79ff02e0e65618609ea02981f4ca520d
[4/5] client: allow skipping signature check on previous manifest fetching
commit: b80847b554be38f7a9bcae9bf09e14dfb64afa22
[5/5] sync: push: gracefully handle previous manifest signature mismatches
commit: bb3a5fdfcfde5324a5b15a34e72138273df69c7e
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-07-29 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 9:07 [PATCH proxmox-backup v3 0/5] restrict previous manifest reuse checks for push sync jobs Christian Ebner
2026-07-29 9:07 ` [PATCH proxmox-backup v3 1/5] datastore: data blob: refactor crypt mode method Christian Ebner
2026-07-29 9:07 ` [PATCH proxmox-backup v3 2/5] datastore: data blob: refactor decoding method Christian Ebner
2026-07-29 9:07 ` [PATCH proxmox-backup v3 3/5] client: backup writer: pass no crypt config to manifest blob decoder Christian Ebner
2026-07-29 9:07 ` [PATCH proxmox-backup v3 4/5] client: allow skipping signature check on previous manifest fetching Christian Ebner
2026-07-29 9:07 ` [PATCH proxmox-backup v3 5/5] sync: push: gracefully handle previous manifest signature mismatches Christian Ebner
2026-07-29 13:00 ` Fabian Grünbichler [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=178533005540.644993.6938528626229983453.b4-ty@proxmox.com \
--to=f.gruenbichler@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