Article 4GPXJ acme-client(1) moves to Let's Encrypt v02 API

acme-client(1) moves to Let's Encrypt v02 API

by
from OpenBSD Journal on (#4GPXJ)

Florian Obser (florian@) hascommittedthe changes required to moveacme-client(1)in -current to theRFC 8555protocol used by theLet's Encrypt v02 API:

CVSROOT:/cvsModule name:srcChanges by:florian@cvs.openbsd.org2019/06/07 02:07:52Modified 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 v01API. Users must change the api url in /etc/acme-client.conf tohttps://acme-v02.api.letsencrypt.org/directoryExisting accounts (and certs of course) stay valid and after the urlchange acme-client will be able to renew certs.Tested by Renaud Allard and bennoInput & OK benno

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

External Content
Source RSS or Atom Feed
Feed Location http://undeadly.org/cgi?action=rss
Feed Title OpenBSD Journal
Feed Link http://undeadly.org/
Reply 0 comments