** 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 default configuration. This is because as part of pushing people towards the standardized version of the protocol, Let's Encrypt is no longer letting people create new accounts on their ACMEv1 endpoint. More details about this change can be found at https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430. What this means for Ubuntu users is that new Certbot installations on affected systems would need to be given the URL of an alternative ACME server in order to work. Existing installations would be unaffected for now as long as they don't deactivate their account or delete its credentials. They will have additional problems in the future due to the additional deprecations described in the link above. To solve this problem, I recommend backporting the Certbot packages from Cosmic to Bionic and Xenial. There are no breaking changes to the public interfaces between versions and I think this results in the smallest change to the packages that would resolve this problem while sticking to well tested packages. [Test Case] The test case will be about requesting a real certificate from Let's Encrypt. You need to make sure the host where you are running these instructions: - is reachable from the internet on port 80 - has a public IP - said public IP has a valid DNS record under a public domain name * install certbot with the apache plugin: sudo apt install python-certbot-apache certbot * run the certbot command: sudo certbot run * After the question about your email address, it will initiate a connection to an ACME server. The old packages will use a V1 server, like this: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org * The new packages will use a v2 server, like this: Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org The above (use a v2 server) is the SRU verification in a nutshell. Of course, obtaining the certificate at the end should still work, but we want to verify with this update that the v2 server was used. Depending on the date this test is run, the acme v1 server might have been deactivated, in which case you will get this error (with the old packages): Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org An unexpected error occurred: The client lacks sufficient authorization :: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details. Please see the logfiles in /var/log/letsencrypt for more details. * To complete the test, let's test renewing the certificate, and then revoke it: sudo certbot --dry-run renew * list certificates, taking note of the certificate path: sudo certbot certificate * revoke the certificate, using the certificate path obtained in the previous step: sudo certbot --cert-path <path-from-previous-step> revoke * As a final testing step, list the systemd timers, to make sure the certbot one is active: $ sudo systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES Fri 2019-10-11 04:38:08 UTC 8h left Thu 2019-10-10 19:24:55 UTC 1h 1min ago certbot.timer certbot.service ... - [Regression Potential] The fix adopted for this bug is a backport from a newer package (cosmic). No changes at all for bionic, but xenial needed some: - no python3 in xenial, so I had to go back to py2. Upstream gave us their ok (see comment #8) - debhelper 9 instead of 11, that required some changes too, specially around systemd - build-depends on sphinx >= 1.6 had to be removed, and was done following upstream's guidance (see comment #6) [Other Info] + This SRU depends on bug #1836823 being released first, as the newer python-acme is required. - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance [Original Description] This bug affects the python-certbot packages in Xenial and Bionic. Cosmic and newer is unaffected. 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 default configuration. This is because as part of pushing people towards the standardized version of the protocol, Let's Encrypt is no longer letting people create new accounts on their ACMEv1 endpoint. More details about this change can be found at https://community.letsencrypt.org/t/end-of-life-plan-for- acmev1/88430. What this means for Ubuntu users is that new Certbot installations on affected systems would need to be given the URL of an alternative ACME server in order to work. Existing installations would be unaffected for now as long as they don't deactivate their account or delete its credentials. They will have additional problems in the future due to the additional deprecations described in the link above. To solve this problem, I recommend backporting the Certbot packages from Cosmic to Bionic and Xenial. There are no breaking changes to the public interfaces between versions and I think this results in the smallest change to the packages that would resolve this problem while sticking to well tested packages.
-- 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: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
