From: duluxoz <duluxoz@gmail.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Step-CA And Proxmox
Date: Thu, 15 Aug 2024 17:22:34 +1000 [thread overview]
Message-ID: <361a29e1-029f-4e25-a081-5ec48d0979b0@gmail.com> (raw)
Hi All,
We run an internal PKI using the Step-CA project
(https://smallstep.com/certificates/).
Step-CA can respond to ACME Client requests in exactly the same way that
Let's Encrypt does - you simply point the client ACME App/Script
(Certbot, acme.sh, etc) to the local CA instead of Let's Encrypt's servers.
So our question is: Within Proxmox, which can handle Let's Encrypt
Certs, how do we (is it possible too) point the Proxmox ACME Client to
our internal Step-CA servers? Is there a config setting we've missed, an
Add-On, etc, or something else?
Thanks in advance
Dulux-Oz
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next reply other threads:[~2024-08-15 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 7:22 duluxoz [this message]
2024-08-16 6:38 ` Aaron Lauterer
2024-08-16 7:22 ` duluxoz
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=361a29e1-029f-4e25-a081-5ec48d0979b0@gmail.com \
--to=duluxoz@gmail.com \
--cc=matthew@peregrineit.net \
--cc=pve-user@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