Let’s Encrypt will begin issuing wildcard certificates in January of 2018
-
Let’s Encrypt will begin issuing wildcard certificates in January of 2018. Wildcard certificates are a commonly requested feature and we understand that there are some use cases where they make HTTPS deployment easier. Our hope is that offering wildcards will help to accelerate the Web’s progress towards 100% HTTPS.
https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html
-
Pretty awesome, that'll be quite the game changer.
-
@aaronstuder
With this, I can SSL an internal site and it will show up without and SSL warning message correct ? and for free ?
-
@msff-amman-Itofficer said in Let’s Encrypt will begin issuing wildcard certificates in January of 2018:
@aaronstuder
With this, I can SSL an internal site and it will show up without and SSL warning message correct ? and for free ?
You can do it now, you ust have to figure out how to migrate the certs from the public system to the internal system.
That need will not change. Also you still have to have a proper public DNS name on the internal system because certs work on names. You cannot use a cert on an IP address or an invalid TLD such as .local.
Basically there is no real point to a wildcard SSL cert from a service like this except for a few niche cases. People always asking for it do so because they don't understand things.
-
@JaredBusch said in Let’s Encrypt will begin issuing wildcard certificates in January of 2018:
Basically there is no real point to a wildcard SSL cert from a service like this except for a few niche cases. People always asking for it do so because they don't understand things.
Mostly it existed before so that you didn't have to get as many individual certs, but that doesn't make sense in the free cert world.
-
@JaredBusch said in Let’s Encrypt will begin issuing wildcard certificates in January of 2018:
an do it now, you ust have to figure out how to migrate the certs from the public system to the internal system.
That need will not change. Also you still have to have a proper public DNS name on the internal system because certs work on names. You cannot use a cert on an IP address or an invalid TLD such as .local.
Basically there is no real point to a wildcard SSL cert from a service like this except for a few niche cases. People always asking for it do so because they don't understand things.Would you recommend a SAN Certificate then?
-
@dbeato said in Let’s Encrypt will begin issuing wildcard certificates in January of 2018:
@JaredBusch said in Let’s Encrypt will begin issuing wildcard certificates in January of 2018:
an do it now, you ust have to figure out how to migrate the certs from the public system to the internal system.
That need will not change. Also you still have to have a proper public DNS name on the internal system because certs work on names. You cannot use a cert on an IP address or an invalid TLD such as .local.
Basically there is no real point to a wildcard SSL cert from a service like this except for a few niche cases. People always asking for it do so because they don't understand things.Would you recommend a SAN Certificate then?
All LE certs are SAN is there is more than one domain on it. Go look at the cert on daerma.com
-
@JaredBusch yes, I saw.
