Re: [PATCH proxmox{,-backup} 00/20] fix #7251: implement server side encryption support for push sync jobs

[Christian Ebner <c.ebner@proxmox.com>]

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!