From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2] tape: skip setting encryption if we can't and don't want to
Date: Tue, 22 Jul 2025 19:16:59 +0200 [thread overview]
Message-ID: <175320461617.1800210.14107466070247151662.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250416070703.493585-1-d.csapak@proxmox.com>
On Wed, 16 Apr 2025 09:07:03 +0200, Dominik Csapak wrote:
> Some settings on changers prevents changing the encryption parameters
> via the application, e.g. some libraries have a 'encryption disabled' or
> 'encryption is library managed' option. While the former situation can
> be fixed by setting the library to 'application managed', the latter is
> sometimes necessary for FIPS compliance (to ensure the tape data is
> encrypted).
>
> [...]
Than you for your very thorough follow-up adding much more rationale for me.
With that I can see your point and agree with it.
Applied for PBS 4, we can still backport this though on user demand, thanks!
[1/1] tape: skip setting encryption if we can't and don't want to
commit: 096505eaf7b16aedb5ee75ae874275c95e7b8d0e
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-07-22 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 7:07 Dominik Csapak
2025-04-17 14:10 ` Andrew Stone
2025-07-11 10:09 ` Dominik Csapak
2025-07-11 11:45 ` Thomas Lamprecht
2025-07-11 13:29 ` Dominik Csapak
2025-07-11 15:09 ` Thomas Lamprecht
2025-07-14 6:43 ` Dominik Csapak
2025-07-22 17:16 ` Thomas Lamprecht [this message]
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=175320461617.1800210.14107466070247151662.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-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