From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 754021FF13A for ; Wed, 29 Apr 2026 16:09:46 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 49C06F8CA; Wed, 29 Apr 2026 16:09:46 +0200 (CEST) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pbs-devel@lists.proxmox.com Subject: [PATCH proxmox{,-backup} 0/6] sync: add strict encryption mode Date: Wed, 29 Apr 2026 16:09:21 +0200 Message-ID: <20260429140941.3537494-1-f.gruenbichler@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777471684814 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [jobs.rs,pull.rs,sync.rs,push.rs] Message-ID-Hash: 4FY76RZDI4NXVUULWZD7RCRWKHFVBNQQ X-Message-ID-Hash: 4FY76RZDI4NXVUULWZD7RCRWKHFVBNQQ X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: enabling this mode will ensure that encrypted snapshots using keys other than those configured are not synced. pull in general is currently a bit stricter than push, erroring out as opposed to skipping - should we align the behaviour? proxmox: Fabian Grünbichler (1): pbs-api-types: sync job: add strict-encryption-mode pbs-api-types/src/jobs.rs | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) proxmox-backup: Fabian Grünbichler (5): pull: add support for strict decryption checking push: add support for strict encryption checking sync: wire up strict encryption mode ui: add strict-encryption-mode to SyncJobEdit window docs: sync: add strict encryption mode docs/managing-remotes.rst | 5 +++++ src/api2/config/sync.rs | 30 +++++++++++++++++++++++++++- src/api2/pull.rs | 11 +++++++++-- src/api2/push.rs | 9 ++++++++- src/server/pull.rs | 9 +++++++++ src/server/push.rs | 41 ++++++++++++++++++++++++++++++++++----- src/server/sync.rs | 1 + www/window/SyncJobEdit.js | 17 ++++++++++++++++ 8 files changed, 114 insertions(+), 9 deletions(-) Summary over all repositories: 9 files changed, 128 insertions(+), 13 deletions(-) -- Generated by murpp 0.11.0