Contributed by rueda on 2019-06-07 from the wiley-coyote-and-acme-rockets-go-meep-meep dept.

Florian Obser ( florian@ ) has committed the changes required to move acme-client(1) in -current to the RFC 8555 protocol used by the Let's Encrypt v02 API :

CVSROOT: /cvs Module name: src Changes by: florian@cvs.openbsd.org 2019/06/07 02:07:52 Modified files: usr.sbin/acme-client: acctproc.c acme-client.1 certproc.c extern.h http.c http.h json.c main.c netproc.c Log message: Implement RFC 8555 "Automatic Certificate Management Environment (ACME)" to be able to talk to the v02 Let's Encrypt API. With this acme-client(1) will no longer be able to talk to the v01 API. Users must change the api url in /etc/acme-client.conf to https://acme-v02.api.letsencrypt.org/directory Existing accounts (and certs of course) stay valid and after the url change acme-client will be able to renew certs. Tested by Renaud Allard and benno Input & OK benno

Let's Encrypt has already announced its "End of Life Plan for ACMEv1".