| 2018-06-16 00:12:57 |
Brad Warren |
bug |
|
|
added bug |
| 2018-06-16 01:59:11 |
Simon Quigley |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-06-16 01:59:11 |
Simon Quigley |
bug task added |
|
python-acme (Ubuntu Bionic) |
|
| 2018-06-16 02:02:43 |
Simon Quigley |
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://community.letsencrypt.org/t/acmev2-order-ready-status/62866 and will error out when it sees them.
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://github.com/certbot/certbot/commit/5940ee92ab5c9a9f05f7067974f6e15c9fa3205a applied. I think the latter is the safer option.
Please let me know what I can do to help get this resolved. |
[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://community.letsencrypt.org/t/acmev2-order-ready-status/62866
[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://community.letsencrypt.org/t/acmev2-order-ready-status/62866 and will error out when it sees them.
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://github.com/certbot/certbot/commit/5940ee92ab5c9a9f05f7067974f6e15c9fa3205a applied. I think the latter is the safer option.
Please let me know what I can do to help get this resolved. |
|
| 2018-06-16 02:09:45 |
Simon Quigley |
python-acme (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2018-06-16 02:09:51 |
Simon Quigley |
python-acme (Ubuntu Bionic): status |
New |
In Progress |
|
| 2018-06-16 02:09:52 |
Simon Quigley |
python-acme (Ubuntu Bionic): assignee |
|
Simon Quigley (tsimonq2) |
|
| 2018-06-16 18:24:57 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2018-06-16 18:33:11 |
Robie Basak |
python-acme (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2018-06-16 18:33:12 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-06-16 18:33:14 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2018-06-16 18:33:18 |
Robie Basak |
tags |
|
verification-needed verification-needed-bionic |
|
| 2018-06-20 18:45:54 |
Launchpad Janitor |
python-acme (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-06-20 18:51:39 |
Robie Basak |
python-acme (Ubuntu): status |
New |
Fix Released |
|
| 2019-02-09 07:13:41 |
Mathew Hodson |
python-acme (Ubuntu): importance |
Undecided |
High |
|
| 2019-02-09 07:15:46 |
Mathew Hodson |
tags |
verification-needed verification-needed-bionic |
verification-done verification-done-bionic |
|
