public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Jakob Klocker <j.klocker@proxmox.com>, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v3 2/3] fix #6990: server: drop verify state on push job
Date: Fri, 25 Sep 2026 12:17:34 +0200	[thread overview]
Message-ID: <0120fe7b-8ec5-4ca8-bb6e-7e3d3cd9a91d@proxmox.com> (raw)
In-Reply-To: <20260922131110.313302-3-j.klocker@proxmox.com>

On 9/22/26 3:11 PM, Jakob Klocker wrote:
> When pushing a snapshot the target manifest is recreated from the source
> manifest, copying its verify_state. As with pull, this makes the pushed
> snapshot appear verified on the remote without its stored copy having
> been checked there.
> Strip verify_state after copying the unprotected section so the pushed
> snapshot is verified independently on the target.
> 
> Link: https://bugzilla.proxmox.com/show_bug.cgi?id=6990
> Signed-off-by: Jakob Klocker <j.klocker@proxmox.com>

As on the last version of the patches, consider:

Reviewed-by: Christian Ebner <c.ebner@proxmox.com>

> ---
>   src/server/push.rs | 7 +++++++
>   1 file changed, 7 insertions(+)
> 
> diff --git a/src/server/push.rs b/src/server/push.rs
> index 487fd91e3..0b754ac2b 100644
> --- a/src/server/push.rs
> +++ b/src/server/push.rs
> @@ -1453,6 +1453,13 @@ pub(crate) async fn push_snapshot(
>       } else {
>           target_manifest.signature = source_manifest.signature.clone();
>       };
> +
> +    if let Some(unprotected) = target_manifest.unprotected.as_object_mut() {
> +        unprotected.remove("verify_state");
> +    } else {
> +        bail!("Encountered unexpected manifest without 'unprotected' section.");
> +    }
> +
>       // FIXME: replace me with to_data_blob once there is an upload_blob
>       let manifest_string =
>           target_manifest.to_string(encrypt_using_key.map(|(_, config)| config).as_deref())?;





  reply	other threads:[~2026-09-25 10:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 13:11 [PATCH proxmox-backup v3 0/3] fix #6990: server: drop verify state on push & pull job Jakob Klocker
2026-09-22 13:11 ` [PATCH proxmox-backup v3 1/3] server: pull: run blocking file operations on the blocking pool Jakob Klocker
2026-09-25 10:17   ` Christian Ebner
2026-09-22 13:11 ` [PATCH proxmox-backup v3 2/3] fix #6990: server: drop verify state on push job Jakob Klocker
2026-09-25 10:17   ` Christian Ebner [this message]
2026-09-22 13:11 ` [PATCH proxmox-backup v3 3/3] fix #6990: server: drop verify state on non-decrypt pull job Jakob Klocker
2026-09-25 10:17   ` Christian Ebner
2026-09-25 10:20 ` [PATCH proxmox-backup v3 0/3] fix #6990: server: drop verify state on push & " Christian Ebner

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=0120fe7b-8ec5-4ca8-bb6e-7e3d3cd9a91d@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=j.klocker@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal