This bug was fixed in the package python-certbot -
0.27.0-1~ubuntu16.04.1
---
python-certbot (0.27.0-1~ubuntu16.04.1) xenial; urgency=medium
* Backport to xenial (LP: #1837673):
- d/control, d/compat: go back to debhelper 9, and drop R³
-
This bug was fixed in the package python-certbot -
0.27.0-1~ubuntu18.04.1
---
python-certbot (0.27.0-1~ubuntu18.04.1) bionic; urgency=medium
* Backport to bionic (LP: #1837673):
- d/letsencrypt.postrm: purging the transitional package shouldn't
remove the logs (Closes:
Just a reminder that in https://community.letsencrypt.org/t/end-of-life-
plan-for-acmev1/88430/3, Let's Encrypt moved the date where they would
be making this change permanently to October 31st instead of November
1st.
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
Certbot will be unable to create new ACME accounts
To manage notifications about this bug go to:
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
Certbot will be unable to create new ACME accounts
Please remember that this update can only be released after #1836823 is
released as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
Certbot will be unable to create new ACME
bionic verification
Verifying current version uses the v1 endpoint:
$ sudo certbot run
...
In bionic, for some reason (debug level?) the acme url is not shown in the
normal output, so I checked the log at /var/log/letsencrypt/letsencrypt.log and
there it was, v1 was used:
2019-10-25
My xenial verification
First, reproducing the problem:
$ sudo certbot run
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Enter email address (used for urgent renewal and security notices) (Enter 'c' to
cancel):
I tested this finding no problems using the same approach described in
https://bugs.launchpad.net/ubuntu/+source/python-
certbot/+bug/1837673/comments/11.
The output of dpkg-query about the relevant installed packages was:
Xenial:
certbot 0.27.0-1~ubuntu16.04.1
letsencrypt 0.27.0-1~ubuntu16.04.1
Hello Brad, or anyone else affected,
Accepted python-certbot into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
certbot/0.27.0-1~ubuntu18.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/python-certbot/+git/python-certbot/+merge/374375
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/python-certbot/+git/python-certbot/+merge/374376
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/python-certbot/+git/python-certbot/+merge/374373
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
I tested the packages in the PPA on Ubuntu 16.04 and 18.04 using the
steps described at
https://wiki.ubuntu.com/StableReleaseUpdates/Certbot#SRU_Verification_Process.
When testing, if you start with a clean /var/log/letsencrypt directory
and don't include any flags to change the default server
** Description changed:
[Impact]
To do almost anything in the ACME protocol used by Let's Encrypt and Certbot
including obtaining and revoking certificates, you need to first create an
account with the ACME server. Starting in November, Certbot will no longer be
able to do that with its
** Description changed:
[Impact]
To do almost anything in the ACME protocol used by Let's Encrypt and Certbot
including obtaining and revoking certificates, you need to first create an
account with the ACME server. Starting in November, Certbot will no longer be
able to do that with its
** Description changed:
[Impact]
To do almost anything in the ACME protocol used by Let's Encrypt and Certbot
including obtaining and revoking certificates, you need to first create an
account with the ACME server. Starting in November, Certbot will no longer be
able to do that with its
** Changed in: python-certbot (Ubuntu Xenial)
Assignee: James Hebden (ec0) => Andreas Hasenack (ahasenack)
** Changed in: python-certbot (Ubuntu Bionic)
Assignee: James Hebden (ec0) => Andreas Hasenack (ahasenack)
** Changed in: python-certbot (Ubuntu Xenial)
Status: Triaged =>
Ok, this ppa is ready for testing:
https://launchpad.net/~ahasenack/+archive/ubuntu/october-certbot-sru/
Or:
sudo add-apt-repository ppa:ahasenack/october-certbot-sru
I was able to verify today that the existing xenial client indeed stopped
working (we are in the first brown-out day):
py2 build updated and uploaded to the ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
Certbot will be unable to create new ACME accounts
To manage notifications about this bug go
> Their py2 counterparts are of course available, but this means we
won't be producing python3-certbot packages, just python-certbot (if
0.27.0 works with py2, that is).
I personally think this is fine. We just have to make sure the "certbot"
package depends on and uses python-certbot rather than
There are other changes needed in the backport from cosmic.
Specifically, python3 support.
The xenial certbot packages are py2 currently, and not all py3
dependencies needed by the cosmic package are available in xenial. These
two are missing:
- python3-parsedatetime
-
To fix the issues building the python-certbot-doc package on Xenial, you
essentially want to revert the commit
https://github.com/certbot/certbot/commit/d8057f0e17dc757fae662dad91a6fedc96ad6a2d.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
PPA with test packages (still building certbot for bionic atm):
https://launchpad.net/~ahasenack/+archive/ubuntu/october-certbot-sru/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
> To solve this problem, I recommend backporting the Certbot packages from
> Cosmic to Bionic
> and Xenial.
Cosmic, which is EOL now, had 0.27.0-1:
python-certbot (0.27.0-1) unstable; urgency=medium
* New upstream version 0.27.0
* Refresh patch after upstream migration to codecov
* Bump
Let's Encrypt just announced brown-outs where they will be temporarily
making this change at https://community.letsencrypt.org/t/end-of-life-
plan-for-acmev1/88430/3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
James, have you managed to make any progress on these SRUs yet please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837673
Title:
Certbot will be unable to create new ACME accounts
To manage
** Changed in: python-certbot (Ubuntu)
Assignee: (unassigned) => James Hebden (ec0)
** Changed in: python-certbot (Ubuntu Xenial)
Assignee: (unassigned) => James Hebden (ec0)
** Changed in: python-certbot (Ubuntu Bionic)
Assignee: (unassigned) => James Hebden (ec0)
--
You
I forgot to mention two potential hurdles:
1. python-acme needs to be updated before backporting python-certbot. This
needs to be done anyway by November though as described at
https://bugs.launchpad.net/ubuntu/+source/python-acme/+bug/1836823.
2. One potential problem for Xenial is that the
** Also affects: python-certbot (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: python-certbot (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: python-certbot (Ubuntu Xenial)
Status: New => Triaged
** Changed in: python-certbot
30 matches
Mail list logo
