From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox-backup 0/3] fixup client log fetching and decryption
Date: Sat, 25 Apr 2026 16:09:24 +0200 [thread overview]
Message-ID: <20260425140927.928214-1-c.ebner@proxmox.com> (raw)
This patches fix a few issues with the client log fetching for pull
sync jobs:
1. Local pull syncs did not fetch the client log at all, add the
missing implementation thereof.
2. While fetching the client log, some logs were still not using the
log line sender, required since introduction of the parallel group
sync feature for correctly buffering and logging lines with prefix.
3. The client log was fetched without decryption even with a matching
decryption key. This is fixed by factoring out the data blob
decryption logic into a reusable helper function and using it in
combination with the crypt config to decrypt the blobs while
fetching the client log.
Christian Ebner (3):
sync: fix client log fetching for local sync job
sync: use log sender for logging when fetching client log
sync: decrypt client log on pull with matching decryption key
src/server/pull.rs | 46 +++++++----------
src/server/sync.rs | 125 +++++++++++++++++++++++++++++++++++++--------
2 files changed, 122 insertions(+), 49 deletions(-)
--
2.47.3
next reply other threads:[~2026-04-25 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-25 14:09 Christian Ebner [this message]
2026-04-25 14:09 ` [PATCH proxmox-backup 1/3] sync: fix client log fetching for local sync job Christian Ebner
2026-04-25 14:09 ` [PATCH proxmox-backup 2/3] sync: use log sender for logging when fetching client log Christian Ebner
2026-04-25 14:09 ` [PATCH proxmox-backup 3/3] sync: decrypt client log on pull with matching decryption key Christian Ebner
2026-04-25 19:37 ` applied: [PATCH proxmox-backup 0/3] fixup client log fetching and decryption Thomas Lamprecht
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=20260425140927.928214-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox