On 2023/4/19 02:16, James Knott wrote:
isn't enough. As someone else mentioned, you can't access https sites. I also tried playing with using the addresses many years ago and soon stopped bothering with them. I have some experience about playing the https://ipv4-address/
I use the openssl to create a private CA. Then use this CA to create/sign a server certificate. In the server certificate, I listed the IP address in the "Subject Alternative Name". You can see the manual page for openssl's x509v3_config. Assume that the IP address in the certificate is 192.168.0.123, it's a linux box. In the 192.168.0.123, I run below openssl command openssl s_server -accept 192.168.0.123:4433 -www -cert my-private-ip.crt -key my-private-ip.key On the other side. I run firefox from another PC that installed and trust the private CA then try to connect to the https://192.168.0.123:4433/. Guess what, it worked. On the manual page of x509v3_config, it also supports IPv6 address as the Subject Alternative Name.