Let’s Encrypt to transition to ISRG root
scotthelme.co.uk
Let’s Encrypt to transition to ISRG root
1–10 of 114 posts
Re: Let’s Encrypt to transition to ISRG root
#2ISRG stands for Internet Security Research Group.
Re: Let’s Encrypt to transition to ISRG root
#3ISRG stands for Internet Security Research Group.
And ISRG is the non-profit legal entity behind Let's Encrypt:
Re: Let’s Encrypt to transition to ISRG root
#4They haven't really published a list of good/bad clients. I'm interested in what's the practical cutoff point with mobile phones? I expect desktop browsers will be less of an issue.
Re: Let’s Encrypt to transition to ISRG root
#5Is it still hard to do wildcard certs with them? That is one of the reasons I don't use let's encrypt.
Re: Let’s Encrypt to transition to ISRG root
#6They haven't really published a list of good/bad clients. I'm interested in what's the practical cutoff point with mobile phones? I expect desktop browsers will be less of an issue.
They provide a test site. It works on my Android One: https://valid-isrgrootx1.letsencrypt.org/
People with other versions of Android and iOS can test and report here?
Re: Let’s Encrypt to transition to ISRG root
#7Is it still hard to do wildcard certs with them? That is one of the reasons I don't use let's encrypt.
It's easier now with ACME v2 and using DNS for authentication or whatever.
Re: Let’s Encrypt to transition to ISRG root
#8Is it still hard to do wildcard certs with them? That is one of the reasons I don't use let's encrypt.
It’s easy if you have a DNS provider for which there is a DNS-auth module.
This was one of the reasons for me switching to Cloudflare DNS, although many other providers should work too.
Re: Let’s Encrypt to transition to ISRG root
#9Re: Let’s Encrypt to transition to ISRG root
#10Is it still hard to do wildcard certs with them? That is one of the reasons I don't use let's encrypt.
Hard in what way? Using my favorite client/library (https://go-acme.github.io/lego/) I can generate wildcard cert with:
lego \
--email="info@example.com" \
--accept-tos \
--path="./ssl" \
--domains="*.example.com" \
--dns="route53"