From: Shannon Sterz <s.sterz@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH proxmox] client: handle tls verification errors more gracefully
Date: Tue, 2 Dec 2025 12:22:36 +0100 [thread overview]
Message-ID: <20251202112235.215074-2-s.sterz@proxmox.com> (raw)
this makes it so that errors that previously would simply yield a
"client error (Connect)" now show a more useful error message, such
as:
Could not establish a TLS connection. Check whether the fingerprint
matches or the certificate is valid. OpenSSL Error: error:0A000086:SSL
routines:tls_post_process_server_certificate:certificate verify
failed:../ssl/statem/statem_clnt.c:2123:
this should help users figure out what's really happened more easily.
Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
---
there might also be one or two bugs hiding in how the client handles
certificate validation. imo setting a fingerprint should override
certificate validity and not the other way round. as it is somewhat akin
to pinning a certificate.
also as fabian pointed out in an off list discussion, the use of
`current_cert` in `verify_fingerprint` may be wrong as it could yield a
parent certificate if it is already unverifiable by openssl. this one
would need some more investigation, though.
left both of these as-is, as that seems like some bigger changes for
right now.
proxmox-client/src/client.rs | 42 ++++++++++++++++++++++++++++--------
1 file changed, 33 insertions(+), 9 deletions(-)
diff --git a/proxmox-client/src/client.rs b/proxmox-client/src/client.rs
index da2c5c59..81af5681 100644
--- a/proxmox-client/src/client.rs
+++ b/proxmox-client/src/client.rs
@@ -242,10 +242,22 @@ impl Client {
}
.map_err(|err| Error::internal("failed to build request", err))?;
- let response = client
- .request(request)
- .await
- .map_err(|err| Error::Client(err.into()))?;
+ let response = client.request(request).await.map_err(|err| {
+ for err in err.chain() {
+ if let Some(err) = err.downcast_ref::<openssl::error::ErrorStack>() {
+ return Error::Client(
+ format!(
+ "Could not establish a TLS connection. Check \
+ whether the fingerprint matches or the certificate is valid. \
+ OpenSSL Error: {err}"
+ )
+ .into(),
+ );
+ }
+ }
+
+ Error::Client(err.into())
+ })?;
if response.status() == StatusCode::UNAUTHORIZED {
return Err(Error::Unauthorized);
@@ -352,11 +364,23 @@ impl Client {
.body(request.body.into())
.map_err(|err| Error::internal("error building login http request", err))?;
- let api_response = self
- .client
- .request(request)
- .await
- .map_err(|err| Error::Client(err.into()))?;
+ let api_response = self.client.request(request).await.map_err(|err| {
+ for err in err.chain() {
+ if let Some(err) = err.downcast_ref::<openssl::error::ErrorStack>() {
+ return Error::Client(
+ format!(
+ "Could not establish a TLS connection. Check \
+ whether the fingerprint matches or the certificate is valid. \
+ OpenSSL Error: {err}"
+ )
+ .into(),
+ );
+ }
+ }
+
+ Error::Client(err.into())
+ })?;
+
if !api_response.status().is_success() {
return Err(Error::api(api_response.status(), "authentication failed"));
}
--
2.47.3
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next reply other threads:[~2025-12-02 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 11:22 Shannon Sterz [this message]
2025-12-03 10:53 ` [pdm-devel] applied: " Lukas Wagner
2025-12-03 12:22 ` [pdm-devel] " 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=20251202112235.215074-2-s.sterz@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pdm-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