From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied: [PATCH proxmox-backup 0/3] fixup for server side decryption
Date: Fri, 24 Apr 2026 21:06:47 +0200 [thread overview]
Message-ID: <177705760873.3360887.6464337368473148301.b4-ty@b4> (raw)
In-Reply-To: <20260424103607.531400-1-c.ebner@proxmox.com>
On Fri, 24 Apr 2026 12:36:04 +0200, Christian Ebner wrote:
> When decryption keys are set for a pull job, currently it is not
> correctly distinguished whether the snapshot to be pulled is trueley
> encrypted or just signed, for both cases the key fingerprint being
> present on the manifest. Fix this by explicitley checking each files
> blob crypt mode as registered in the manifest. Further, extend error
> messages on key mismatch with pre-existing local manifests to also
> include the signed-only case.
>
> [...]
Applied, thanks!
[1/3] sync: pull decrypt: check if contents only signed or fully encrypted
commit: f515516448250afc96f3227d1323e0323ded0dda
[2/3] sync: pull: refactor decryption key loading checks
commit: 14b580739d9f0e3ad2098812a3a9b251ae5e48c1
[3/3] api: encryption keys: refactor associated keys check
commit: a6dfa6abdea8045b82209bb357e21862d88b0abc
prev parent reply other threads:[~2026-04-24 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 10:36 Christian Ebner
2026-04-24 10:36 ` [PATCH proxmox-backup 1/3] sync: pull decrypt: check if contents only signed or fully encrypted Christian Ebner
2026-04-24 10:36 ` [PATCH proxmox-backup 2/3] sync: pull: refactor decryption key loading checks Christian Ebner
2026-04-24 12:46 ` Fabian Grünbichler
2026-04-24 10:36 ` [PATCH proxmox-backup 3/3] api: encryption keys: refactor associated keys check Christian Ebner
2026-04-24 12:46 ` [PATCH proxmox-backup 1/2] pull: decrypt: use let else to reduce indentation Fabian Grünbichler
2026-04-24 12:46 ` [PATCH proxmox-backup 2/2] pull: decrypt: re-order encryption key/state checks Fabian Grünbichler
2026-04-24 19:06 ` 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=177705760873.3360887.6464337368473148301.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