Update to use ACMEv2 protocol

[nlepisto]

I've just started getting these notifications: Beginning June 1, 2020, we will stop allowing new domains to validate using the ACMEv1 protocol. You should upgrade to an ACMEv2 compatible client before then, or certificate issuance will fail.

Can this library be updated to use the new v2 protocol or do I need to find another solution?

[alex]

I'm not using this package anymore, or spending time maintaining. I'd recommend you find another solution.

[nlepisto]

Gotcha. I was wondering if it could be as simple as using this instead: DEFAULT_ACME_DIRECTORY_URL = "https://acme-v02.api.letsencrypt.org/directory"

[alex]

It's entirely possible there's a trivial fix -- if there is one I'm happy to merge a PR, but I'm not able to do the research to figure it out.

…

On Sun, Mar 8, 2020 at 1:55 PM Nick Lepisto ***@***.***> wrote: Gotcha. I was wondering if it could be as simple as using this instead: DEFAULT_ACME_DIRECTORY_URL = "https://acme-v02.api.letsencrypt.org/directory" — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#104?email_source=notifications&email_token=AAAAGBERROOLFS6ZBFWCGGDRGPS3NA5CNFSM4LDUXY2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOE4SVA#issuecomment-596232532>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAGBEJKM3FCSUBUCYLXGTRGPS3NANCNFSM4LDUXY2A> .

-- All that is necessary for evil to succeed is for good people to do nothing.