I’m an upstream maintainer of python-acme.
Both Let’s Encrypt [1] and the Certbot client which uses this library encourage
people to use Let’s Encrypt’s staging endpoint to test that they have things
working correctly before using Let’s Encrypt’s production endpoint which has
strict rate limits
I just wanted to make sure this was still on everyone’s radar. The change
server side where tens of thousands of Debian users will begin being unable to
renew their certificates is in less than a month.
> On Jan 8, 2019, at 4:24 PM, Harlan Lieberman-Berg wrote:
>
> Hello Julien, everyone,
>
>
What can be done to get this issue resolved?
This issue has jumped in priority now that domain validation through the
TLS-SNI-01 challenge will be completely unsupported by Let’s Encrypt on
February 13th, 2019. See
https://community.letsencrypt.org/t/february-13-2019-end-of-life-for-all-tls-sni
I’m another upstream developer of Certbot.
Taking 0.21.1 into stable would be the most conservative update that would
resolve this issue. The oldest version you could take is 0.21.0, but 0.21.1 was
released 8 days later and as a result has been much more widely tested. Since
0.21.1 was released
4 matches
Mail list logo
