The underlying upstream issue was: https://github.com/certbot/certbot/pull/2529
However we would strongly, strongly recommend updating Certbot users to 0.8.1-2 rather than leaving them with a letsencrypt 0.4.1. There are plenty of serious issues that have been fixed in between. The full list of issues resolved between 0.4.1 and 0.8.1-2 is the combination of all of these lists: https://github.com/certbot/certbot/issues?q=is%3Aissue+milestone%3A0.4.2+is%3Aclosed https://github.com/certbot/certbot/issues?q=is%3Aissue%20is%3Aclosed%20milestone%3A0.5.0 https://github.com/certbot/certbot/issues?q=is%3Aissue%20is%3Aclosed%20milestone%3A0.6.0 https://github.com/certbot/certbot/issues?q=is%3Aissue%20is%3Aclosed%20milestone%3A0.7.0 https://github.com/certbot/certbot/issues?q=is%3Aissue%20is%3Aclosed%20milestone%3A0.8.0 https://github.com/certbot/certbot/issues?q=is%3Aissue%20is%3Aclosed%20milestone%3A0.8.1 0.8.1-2 has been in the field for over a month, and we believe it is stable and working well for users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610030 Title: certbot improperly encodes CSRs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1610030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
