[GH-ISSUE #7] Add more configuration for how to connect to Proxmox #4

Open
opened 2026-03-14 08:23:13 +03:00 by kerem · 0 comments
Owner

Originally created by @andrew-d on GitHub (Apr 11, 2025).
Original GitHub issue: https://github.com/andrew-d/proxmox-service-discovery/issues/7

As observed in #4, it's possible that the URL/IP address that is used to connect to Proxmox doesn't match the name on the certificate, or that a self-signed or private CA certificate is in use. In #6, we added a flag to disable TLS certificate verification, but that's a bit of a blunt hammer. Instead, we should add more fine-grained flags to allow the user to control what they connect to. At the very least:

  • Allow the user to provide an additional or alternate CA root to verify
  • Allow specifying the name on the certificate to verify, distinct from the IP/hostname used to connect
Originally created by @andrew-d on GitHub (Apr 11, 2025). Original GitHub issue: https://github.com/andrew-d/proxmox-service-discovery/issues/7 As observed in #4, it's possible that the URL/IP address that is used to connect to Proxmox doesn't match the name on the certificate, or that a self-signed or private CA certificate is in use. In #6, we added a flag to disable TLS certificate verification, but that's a bit of a blunt hammer. Instead, we should add more fine-grained flags to allow the user to control what they connect to. At the very least: - [ ] Allow the user to provide an additional or alternate CA root to verify - [ ] Allow specifying the name on the certificate to verify, distinct from the IP/hostname used to connect
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/proxmox-service-discovery#4
No description provided.