<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Certbot 0.34.0 was just released. The changelog for the release is:<br>
<br>
## 0.34.0 - 2019-05-01<br>
<br>
### Changed<br>
<br>
* Apache plugin now tries to restart httpd on Fedora using systemctl
if a<br>
configuration test error is detected. This has to be done due to
the way<br>
Fedora now generates the self signed certificate files upon first<br>
restart.<br>
* Updated Certbot and its plugins to improve the handling of file
system permissions<br>
on Windows as a step towards adding proper Windows support to
Certbot.<br>
* Updated urllib3 to 1.24.2 in certbot-auto.<br>
* Removed the fallback introduced with 0.32.0 in `acme` to retry a
challenge response<br>
with a `keyAuthorization` if sending the response without this
field caused a<br>
`malformed` error to be received from the ACME server.<br>
* Linode DNS plugin now supports api keys created from their new
panel<br>
at [cloud.linode.com](<a class="moz-txt-link-freetext" href="https://cloud.linode.com">https://cloud.linode.com</a>)<br>
* Adding a warning noting that future versions of Certbot will
automatically configure the<br>
webserver so that all requests redirect to secure HTTPS access.
You can control this<br>
behavior and disable this warning with the --redirect and
--no-redirect flags.<br>
* certbot-auto now prints warnings when run as root with insecure
file system<br>
permissions. If you see these messages, you should fix the problem
by<br>
following the instructions at<br>
<a class="moz-txt-link-freetext" href="https://community.letsencrypt.org/t/certbot-auto-deployment-best-practices/91979/">https://community.letsencrypt.org/t/certbot-auto-deployment-best-practices/91979/</a>,<br>
however, these warnings can be disabled as necessary with the flag<br>
--no-permissions-check.<br>
* `acme` module uses now a POST-as-GET request to retrieve the
registration<br>
from an ACME v2 server<br>
* Convert the tsig algorithm specified in the certbot_dns_rfc2136
configuration file to<br>
all uppercase letters before validating. This makes the value in
the config case<br>
insensitive.<br>
<br>
Despite us having broken lockstep, we are continuing to release new
versions of<br>
all Certbot components during releases for the time being, however,
the only<br>
package with changes other than its version number was:<br>
<br>
* acme<br>
* certbot<br>
* certbot-apache<br>
* certbot-dns-cloudflare<br>
* certbot-dns-cloudxns<br>
* certbot-dns-digitalocean<br>
* certbot-dns-dnsimple<br>
* certbot-dns-dnsmadeeasy<br>
* certbot-dns-gehirn<br>
* certbot-dns-google<br>
* certbot-dns-linode<br>
* certbot-dns-luadns<br>
* certbot-dns-nsone<br>
* certbot-dns-ovh<br>
* certbot-dns-rfc2136<br>
* certbot-dns-route53<br>
* certbot-dns-sakuracloud<br>
* certbot-nginx<br>
<br>
More details about these changes can be found on our GitHub repo.
</body>
</html>