From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH installer] common: http: add custom ureq connector for cert-fingerprint validation
Date: Wed, 25 Jun 2025 15:26:27 +0200 [thread overview]
Message-ID: <175085798124.449686.6453094750889880141.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250625122229.1115619-1-c.heiss@proxmox.com>
On Wed, 25 Jun 2025 14:22:01 +0200, Christoph Heiss wrote:
> Adds back custom TLS fingerprint validation for ureq 3. The API was
> changed majorly, no longer providing the possibility to directly provide
> a rustls `ClientConfig` to the agent.
>
> Instead, a complete custom transport + connector must be provided to
> ureq to achieve this.
>
> [...]
Applied, thanks!
[1/1] common: http: add custom ureq connector for cert-fingerprint validation
commit: b877bc184bf43156da1daeaf0fe05bf826aea1e1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-06-25 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 12:22 [pve-devel] " Christoph Heiss
2025-06-25 13:26 ` 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=175085798124.449686.6453094750889880141.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@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