From: Dietmar Maurer <dietmar@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Hannes Laimer <h.laimer@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2 0/3] close #3612: allow config of SSL cipher-suites for proxy
Date: Wed, 5 Jan 2022 10:27:21 +0100 (CET) [thread overview]
Message-ID: <1064698276.2596.1641374841394@webmail.proxmox.com> (raw)
> But this does not throw an error:
>
> # proxmox-backup-manager node update --cipher-suites-tls2 asdasd,BBB,BBB.XZY,ECDHE-RSA-AES256-SHA
>
> Seems ssl simply ignores all unknown ciphers. The only error is when the list contains no known cipher.
I wonder if we can hardcode the list of available values and parse it correctly? Allowed values would be:
# openssl ciphers -tls1_2
# openssl ciphers -tls1_3
next reply other threads:[~2022-01-05 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 9:27 Dietmar Maurer [this message]
2022-01-05 13:53 ` Hannes Laimer
-- strict thread matches above, loose matches on Subject: below --
2022-01-05 15:16 Dietmar Maurer
2022-01-05 9:09 Dietmar Maurer
2022-01-05 8:55 Dietmar Maurer
2022-01-04 11:48 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=1064698276.2596.1641374841394@webmail.proxmox.com \
--to=dietmar@proxmox.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox