python-acme to start crashing on June 19th
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-acme (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Simon Quigley |
Bug Description
[Impact]
Without this fix, on June 19, the library will start to fail when using Let's Encrypt's new ACMEv2 endpoint. We should avoid breaking this for users.
[Test Case]
On June 19, try to use Let's Encrypt's new ACMEv2 endpoint; it will error out, as described in https:/
[Regression Potential]
If the endpoint changes again, this will need another update, but the only potential regression I see is server-side, which needs patches on our end to adjust (like in this case).
[Original Bug Description]
I am the upstream maintainer of python-acme. This bug only affects python-acme in Ubuntu 18.04.
Starting on June 19th, this library will start failing when used with Let's Encrypt's new ACMEv2 endpoint. This is because the library does not recognize the changes described in https:/
To fix this, python-acme either needs to be upgraded to 0.25.1 (which came out two days ago) or the one line patch that originally landed upstream at https:/
Please let me know what I can do to help get this resolved.
description: | updated |
Changed in python-acme (Ubuntu): | |
importance: | Undecided → High |
tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic |
Uploaded to Bionic.
Assuming this gets accepted into bionic-proposed, I would argue that this needs to be released early, so it can be released to users before error messages start.
Let me know what I can do to help.
Thanks.