问题原文
原帖链接 · BThompson · CC BY-SA 4.0
I am developing a network management product. We ship our product to customers as a VM, which they install on a hypervisor in their network. These VMs are given static, private IP addresses in the customer network. They monitor the customer's devices, and run a (Apache/Django) webserver showing the state of the network. Customers access the site by the private IP and we access the VMs directly using TeamViewer (installed before we ship them), so there's no public IP or domain name involved. We'd very much like to provide SSL certs on our VMs so that clients stop seeing notifications that our site is insecure (and of course, so that our site stops being insecure). Preferably, customers should not have to add trust for a new CA or add security exceptions to their browsers.
What is the most efficient and cost effective way to do so? I have tried LetsEncrypt, but they only support certs for domain names, not for IPs.
社区高分解答
原帖链接 · Esa Jokinen · CC BY-SA 4.0
Just use a self-signed certificate as you already do, and don't try any dirty hacks to bypass the error. Provide your customers an option to replace that certificate with their own. The replacement certificate can be signed by a public CA using their own public (sub) domain name or by a locally trusted CA, e.g. using Active Directory Certificate Services. Either way, it'll always be compatible with their infrastructure and security policy.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
