Weblog

Implementing ACME v2

25 January 2018, 09:50

Some time ago, Let's Encrypt announced that they will be supporting ACME v2 on February 27, 2018. I'm already busy implementing ACME v2 support in Hiawatha's Let's Encrypt client. It's almost finished. There are just some small issues to fix, but those might be a server-side bug as well.

Another new Let's Encrypt feature that's coming in February 2018, is support for wildcard certificates. The issue is that they can only be obtained via a DNS challenge instead of via the HTTP challenge I'm currently using. Using a DNS API is not an option, because not every DNS provider offers an API for DNS changes and there is also no single standard for such API. At the moment, I'm discussing my idea about how to obtain a wildcard certificate via an HTTP challenge with Let's Encrypt and the ACME Working Group at IETF. Hopefully they accept my idea.

Anyone who wants the try the new version of Hiawatha's new Let's Encrypt client, you can download it here.

Elmar Klausmeier

11 February 2018, 17:45

Above link for the beta version of your script gives: 404 Not Found.

Hugo Leisink

12 February 2018, 22:16

It's no longer a beta version. I've updated the link to the new version. Note that you can only request test-certificates with that version.

Heiko

16 February 2018, 23:45

Thank you Hugo.

Let's Encrypt ACME v2 Wildcard is live!

14 March 2018, 06:55

https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579

Almir Bispo

15 December 2018, 00:59

Hello! The Wigwwam and Hiawatha no Windows 7 compatible (32bits). look: http://prntscr.com/lv5b65
Please,send a feed back on gibroh_webmaster@hotmail.com Thank You !

Hugo Leisink

15 December 2018, 17:29

That's right. 64 bit only. You can build a Windows version yourself via Cygwin [www.cygwin.com].