0
I have a private app running as a webserver on a machine on an isolated wifi router using 192.168.1.*/255.255.255.0, with no DNS capability & no upstream Internet; basically, only local wireless. The web server will have one of two IP addresses: 192.168.1.x
or 192.168.1.y
, where x
& y
are fixed values.
What is the incantation of OpenSSL to create a CSR with two IP addresses, such that a client connecting to the web server on one of the two IP addresses would consider the certificate valid? Is there any way to use subjectAltName=
and/or nameConstraints=permitted;IP:192.168.1.???/255.255.255.0
?
It seems like bits & pieces are there, but there are so many options & commands in OpenSSL, I can't tell if this possible.
Are the clients actually accessing the web server by IP address? Do they use URLs like
https://192.168.1.x/...
? – David Schwartz – 2015-11-03T19:21:08.060Yes, by IP address only. – Matthew Adams – 2015-11-04T02:22:45.777