On Sat, Oct 19, 2019 at 08:14:33PM +0200, Florian Zumbiehl wrote: > Is there any plan to fix this bug before then, or will users have to work > around this individually to avoid running into expired certificates? And if > the latter, what is the recommended workaround? Is the current backports > version usable?
The current version in stretch-backports is perfectly usable. It also
moves to the v2 version of the ACME API, which is the only one that
Let's Encrypt now supports.
In fact, the proposed "fix" I'm working on is to actually get the
version that is currently in backports directly in the oldstable
distribution, but I need to tweak it a bit as to do that I need to
reintroduce the 'letsencrypt.sh' compatibility packages/scripts.
So, yes, if you are affected by this bug I recommended to just use the
version in stretch-backports.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
