From: Max Carrara <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v3 manager 0/3] Fix SSL Certificate and Key Upload Issues
Date: Tue, 14 Mar 2023 16:08:36 +0100 [thread overview]
Message-ID: <20230314150839.248059-1-m.carrara@proxmox.com> (raw)
The respective previous versions can be found here:
- v1: https://lists.proxmox.com/pipermail/pve-devel/2023-February/055955.html
- v2: https://lists.proxmox.com/pipermail/pve-devel/2023-March/056011.html
Note: The changes to pve-common are not included in this series
anymore, as they've already been applied.
Testing
-------
The same tests as in v1 were performed.
Changes from v2:
- properly handle cleanup and warnings as well as temp file removal
if setting a new key/cert pair fails[0]
- if given, remove PID from beginning of error message after warning,
making the error message in the UI a little prettier
- use inputpanel widget for certificate upload form before
providing fix for private key upload[1]
Changes from v1:
- properly handle OpenSSL errors[2]
- provide actually correct format changes[3]
- include trailing comma[4]
- make JavaScript code a little more concise[5]
[0] https://lists.proxmox.com/pipermail/pve-devel/2023-March/056047.html
[1] https://lists.proxmox.com/pipermail/pve-devel/2023-March/056063.html
[2] https://lists.proxmox.com/pipermail/pve-devel/2023-March/055962.html
[3] https://lists.proxmox.com/pipermail/pve-devel/2023-March/055963.html
[4] Not on mailing list unfortunately, boo!
[5] https://lists.proxmox.com/pipermail/pve-devel/2023-March/055961.html
pve-manager:
Max Carrara (3):
fix #4552: certhelpers: check if custom cert and key match on change
ui: cert upload: use inputpanel for certificate upload
ui: cert upload: fix private key field sending empty string
PVE/CertHelpers.pm | 70 ++++++++++++++++++----
www/manager6/node/Certificates.js | 99 +++++++++++++++----------------
2 files changed, 105 insertions(+), 64 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-14 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 15:08 Max Carrara [this message]
2023-03-14 15:08 ` [pve-devel] [PATCH v3 manager 1/3] fix #4552: certhelpers: check if custom cert and key match on change Max Carrara
2023-03-22 15:41 ` Max Carrara
2023-03-23 6:08 ` Thomas Lamprecht
2023-03-14 15:08 ` [pve-devel] [PATCH v3 manager 2/3] ui: cert upload: use inputpanel for certificate upload Max Carrara
2023-03-21 15:56 ` [pve-devel] applied: " Thomas Lamprecht
2023-03-14 15:08 ` [pve-devel] [PATCH v3 manager 3/3] ui: cert upload: fix private key field sending empty string Max Carrara
2023-03-21 15:57 ` [pve-devel] applied: " Thomas Lamprecht
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=20230314150839.248059-1-m.carrara@proxmox.com \
--to=m.carrara@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 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.