From: Hannes Laimer <h.laimer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup v3 0/4] close #3612: allow config of SSL cipher-suites for proxy
Date: Sat, 8 Jan 2022 08:08:05 +0100 [thread overview]
Message-ID: <20220108070809.29315-1-h.laimer@proxmox.com> (raw)
Cannot be configured in the WebUI, only through proxmox-backup-manager,
api or in the config file directly(not recommended). For changes to take
effect the proxy has to be restarted.
Since the string can be rather long and I assume most of the time the
defaults are used, it is not in the WebUI.
v2:
- allow setting for TLSv1.3 and TLS <= 1.2 individually
v3:
- add proper regex
Note: if the 2nd patch should be applied, it should probably be squashed
with the 1st one.
Hannes Laimer (4):
config: add tls ciphers to NodeConfig
pbs-api-types: make regex for ciphers more strict
proxy: use ciphers from config if set
api2: make tls ciphers updatable
pbs-api-types/src/lib.rs | 41 +++++++++++++++++++++++++++++++++
src/api2/node/config.rs | 8 +++++++
src/bin/proxmox-backup-proxy.rs | 10 ++++++++
src/config/node.rs | 26 ++++++++++++++++++++-
4 files changed, 84 insertions(+), 1 deletion(-)
--
2.30.2
next reply other threads:[~2022-01-08 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 7:08 Hannes Laimer [this message]
2022-01-08 7:08 ` [pbs-devel] [PATCH proxmox-backup v3 1/4] config: add tls ciphers to NodeConfig Hannes Laimer
2022-01-10 5:40 ` Dietmar Maurer
2022-01-10 8:14 ` Fabian Grünbichler
2022-01-08 7:08 ` [pbs-devel] [PATCH proxmox-backup v3 2/4][optional] pbs-api-types: make regex for ciphers more strict Hannes Laimer
2022-01-08 7:08 ` [pbs-devel] [PATCH proxmox-backup v3 3/4] proxy: use ciphers from config if set Hannes Laimer
2022-01-08 7:08 ` [pbs-devel] [PATCH proxmox-backup v3 4/4] api2: make tls ciphers updatable Hannes Laimer
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=20220108070809.29315-1-h.laimer@proxmox.com \
--to=h.laimer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.