From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id D1CB41FF13B for ; Wed, 08 Apr 2026 17:11:46 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3E820EFDB; Wed, 8 Apr 2026 17:12:29 +0200 (CEST) Message-ID: <7a42d957-4671-4c1a-ad17-ff2d168e4c0a@proxmox.com> Date: Wed, 8 Apr 2026 17:11:54 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH proxmox{,-backup} 00/20] fix #7251: implement server side encryption support for push sync jobs To: David Riley , pbs-devel@lists.proxmox.com References: <20260401075521.176354-1-c.ebner@proxmox.com> <1d62a310-86c5-4586-ad38-b1092bf3cd61@proxmox.com> Content-Language: en-US, de-DE From: Christian Ebner In-Reply-To: <1d62a310-86c5-4586-ad38-b1092bf3cd61@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1775661048007 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.068 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: BFIHC5AWA7AI4PLOSQYKHN2QLXC2VSOS X-Message-ID-Hash: BFIHC5AWA7AI4PLOSQYKHN2QLXC2VSOS X-MailFrom: c.ebner@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: On 4/8/26 9:28 AM, David Riley wrote: > Thanks for your work on this. > I tested your patches for the proxmox and proxmox-backup > repositories and encountered three issues: > > 1. Push/Pull Job: Form validation error > When the encryption key selection is left untouched or disabled, > the form fails validation. > > Reproduction Steps: >   Use two PBS instances (PBS1 with patches, PBS2 without). >   Create a datastore and an encryption key on PBS1. >   Create a datastore on PBS2. >   On PBS1, configure a Push Job for the datastore. >   Leave the Encryption Key field disabled/untouched and submit the >   form. > > The following error appears: > parameter verification errors (400) > encryption-key: value must be at least 3 characters long > > 2. Deleting Encryption Key: "Unknown error" pop-up > > Deleting an encryption key appears to succeed (the key is removed), > but the UI shows an error pop up. > > Error message: "Unknown error" > Observations: No errors are logged in the browser console or the >   network tab. > > 3. Drag and Drop of Encryption Key File > Dragging a file from the file explorer into the "Upload from File" > form field results in a parsing error. > > Reproduction Steps: >   Create Encryption Key and download it. >   Add new key >   Drag and drop the just downloaded key file into the form field. > > The field displays "[object ProgressEvent]" instead of the file > content/name. Hovering over it shows: > "Failed to parse key - SyntaxError: JSON parse unexpected character > at line 1 column 2 of the JSON data" > > Aside from these three points, the rest of the functionality works as > expected. > Thanks a lot for testing and reporting these issues: 1. and 2. have already been reported by others and already fixed for the upcoming version 2. Looking into 3. now, thanks for catching that!