4 ms·

I don't think you need to pay for a domain, nor do you need internet access to renew the certificate. You could either just have the cert point to an IP, or you

I don't think you need to pay for a domain, nor do you need internet access to renew the certificate. You could either just have the cert point to an IP, or you could have the domain resolve to something at the router level/ configure our DNS however you like so that it resolves to the other device. Or you can just disable the strict HTTPS settings, which this post addresses? > We know that enterprises and education networks have unique needs. These features can be turned on early, customized, or turned off entirely via the HttpsOnlyMode, HttpsUpgradesEnabled, HttpAllowlist, and InsecureContentAllowedForUrls policies.

xg15 3y ago
> I don't think you need to pay for a domain, nor do you need internet access to renew the certificate. You could either just have the cert point to an IP, or you could have the domain resolve to something at the router level/ configure our DNS however you like so that it resolves to the other device. If I use a custom root CA, I don't need a domain. However, then my local server will only be accessible on devices where I can install the custom CA, i.e. usually, my own devices only. If I want the server accessible to other people, I need a cert from a real CA - and those are basically forbidden from granting certs for 192.168.* IPs or really anything that is not a properly registered internet domain: https://www.globalsign.com/en/blog/certificates-for-internal-servers https://www.globalsign.com/en/blog/certificates-for-internal... > Or you can just disable the strict HTTPS settings, which this post addresses? That as well works for my own device, but not for devices of other people.
- insanitybit 3y ago
  So the situation is that someone is in your home with their own device and you don't want them to click through the "HTTP" warning? Seems niche tbh but I can understand that I guess.
  - xg15 3y ago
    The HTTP warning may become progressively harder and more confusing to click through, if chrome continues its strategy as they announced in the OP. Usecases would be more something like "shared server in a student dorm / local server for family and friends / art installation where people are supposed to connect their phones to / smart device with a local web server for configuration", etc. Niche indeed compared to the public internet, but still substantial.
    - janosdebugs 3y ago
      How substantial are the situations really where you can't afford a 10-15$ domain and running a trivially simple tool to obtain a certificate? What kind of an art installation has the budget to set up a wifi network, set up servers, etc but then doesn't have internet? (Most phones won't even connect to a wifi network without internet if I remember correctly.)

xg15 3y ago

> I don't think you need to pay for a domain, nor do you need internet access to renew the certificate. You could either just have the cert point to an IP, or you could have the domain resolve to something at the router level/ configure our DNS however you like so that it resolves to the other device. If I use a custom root CA, I don't need a domain. However, then my local server will only be accessible on devices where I can install the custom CA, i.e. usually, my own devices only. If I want the server accessible to other people, I need a cert from a real CA - and those are basically forbidden from granting certs for 192.168.* IPs or really anything that is not a properly registered internet domain: https://www.globalsign.com/en/blog/certificates-for-internal-servers https://www.globalsign.com/en/blog/certificates-for-internal... > Or you can just disable the strict HTTPS settings, which this post addresses? That as well works for my own device, but not for devices of other people.

insanitybit 3y ago
So the situation is that someone is in your home with their own device and you don't want them to click through the "HTTP" warning? Seems niche tbh but I can understand that I guess.
- xg15 3y ago
  The HTTP warning may become progressively harder and more confusing to click through, if chrome continues its strategy as they announced in the OP. Usecases would be more something like "shared server in a student dorm / local server for family and friends / art installation where people are supposed to connect their phones to / smart device with a local web server for configuration", etc. Niche indeed compared to the public internet, but still substantial.
  - janosdebugs 3y ago
    How substantial are the situations really where you can't afford a 10-15$ domain and running a trivially simple tool to obtain a certificate? What kind of an art installation has the budget to set up a wifi network, set up servers, etc but then doesn't have internet? (Most phones won't even connect to a wifi network without internet if I remember correctly.)