All Versions
81
Latest Version
Avg Release Cycle
25 days
Latest Release
1094 days ago

Changelog History
Page 7

  • v0.12.0 Changes

    March 02, 2017

    ➕ Added

    • Certbot now allows non-camelcase Apache VirtualHost names.
    • 🌲 Certbot now allows more log messages to be silenced.

    🛠 Fixed

    • 🛠 Fixed a regression around using --cert-name when getting new certificates

    More information about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/issues?q=is%3Aissue%20milestone%3A0.12.0

  • v0.11.1 Changes

    February 01, 2017

    🛠 Fixed

    • 📜 Resolved a problem where Certbot would crash while parsing command line arguments in some cases.
    • 🛠 Fixed a typo.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/pulls?q=is%3Apr%20milestone%3A0.11.1%20is%3Aclosed

  • v0.11.0 Changes

    February 01, 2017

    ➕ Added

    • 🔌 When using the standalone plugin while running Certbot interactively and a required port is bound by another process, Certbot will give you the option to retry to grab the port rather than immediately exiting.
    • You are now able to deactivate your account with the Let's Encrypt server using the unregister subcommand.
    • When revoking a certificate using the revoke subcommand, you now have the option to provide the reason the certificate is being revoked to Let's Encrypt with --reason.

    🔄 Changed

    • 📦 Providing --quiet to certbot-auto now silences package manager output.

    ✂ Removed

    • ✂ Removed the optional dnspython dependency in our acme package. 👍 Now the library does not support client side verification of the DNS challenge.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/issues?q=is%3Aissue+milestone%3A0.11.0+is%3Aclosed

  • v0.10.2 Changes

    January 25, 2017

    ➕ Added

    • If Certbot receives a request with a badNonce error, it now automatically retries the request. Since nonces from Let's Encrypt expire, 🔌 this helps people performing the DNS challenge with the manual plugin who may have to wait an extended period of time for their DNS changes to propagate.

    🛠 Fixed

    • Certbot now saves the --preferred-challenges values for renewal. Previously these values were discarded causing a different challenge type to be used when renewing certs in some cases.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/issues?q=is%3Aissue+milestone%3A0.10.2+is%3Aclosed

  • v0.10.1 Changes

    January 13, 2017

    🛠 Fixed

    • ⚡️ Resolve problems where when asking Certbot to update a certificate at an existing path to include different domain names, the old names would continue to be used.
    • 🛠 Fix issues successfully running our unit test suite on some systems.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/issues?q=is%3Aissue+milestone%3A0.10.1+is%3Aclosed

  • v0.10.0

    January 11, 2017

  • v0.9.3 Changes

    October 13, 2016

    ➕ Added

    • 🔌 The Apache plugin uses information about your OS to help determine the 🔧 layout of your Apache configuration directory. We added a patch to ✅ ensure this code behaves the same way when testing on different systems ✅ as the tests were failing in some cases.

    🔄 Changed

    • Certbot adopted more conservative behavior about reporting a needed port as 🔌 unavailable when using the standalone plugin.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/27?closed=1

  • v0.9.2 Changes

    October 12, 2016

    ➕ Added

    • Certbot stopped requiring that all possibly required ports are available when 🔌 using the standalone plugin. It now only verifies that the ports are available when they are necessary.

    🛠 Fixed

    • Certbot now verifies that our optional dependencies version matches what is required by Certbot.
    • Certnot now properly copies the ssl on; directives as necessary when 🔌 performing domain validation in the Nginx plugin.
    • 🛠 Fixed problem where symlinks were becoming files when they were 📦 packaged, causing errors during testing and OS packaging.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/26?closed=1

  • v0.9.1 Changes

    October 06, 2016

    🛠 Fixed

    • 🛠 Fixed a bug that was introduced in version 0.9.0 where the command line flag -q/--quiet wasn't respected in some cases.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/milestone/25?closed=1

  • v0.9.0 Changes

    October 05, 2016

    ➕ Added

    • ➕ Added an alpha version of the Nginx plugin. This plugin fully automates the 🖨 process of obtaining and installing certificates with Nginx. ➕ Additionally, it is able to automatically configure security ✨ enhancements such as an HTTP to HTTPS redirect and OCSP stapling. To use 📦 this plugin, you must have the certbot-nginx package installed (which is installed automatically when using certbot-auto) and provide 🔌 --nginx on the command line. This plugin is still in its early stages so we recommend you use it with some caution and make sure you have a 🔧 backup of your Nginx configuration.
    • ➕ Added support for the DNS challenge in the acme library and DNS in 🔌 Certbot's manual plugin. This allows you to create DNS records to prove to Let's Encrypt you control the requested domain name. To use this feature, include --manual --preferred-challenges dns on the 💻 command line.
    • 🐧 Certbot now helps with enabling Extra Packages for Enterprise Linux (EPEL) on CentOS 6 when using certbot-auto. To use certbot-auto on CentOS 6, the EPEL repository has to be enabled. certbot-auto will now prompt 👉 users asking them if they would like the script to enable this for them automatically. This is done without prompting users when using letsencrypt-auto or if -n/--non-interactive/--noninteractive is 💻 included on the command line.

    More details about these changes can be found on our GitHub repo: https://github.com/certbot/certbot/issues?q=is%3Aissue+milestone%3A0.9.0+is%3Aclosed