Certbot 1.1.0 Release

Client dev
1

Certbot 1.1.0 has just been released. The changelog for the release is:

1.1.0 - 2020-01-14

Changed

  • Removed the fallback introduced with 0.34.0 in acme to retry a POST-as-GET
    request as a GET request when the targeted ACME CA server seems to not support
    POST-as-GET requests.
  • certbot-auto no longer supports architectures other than x86_64 on RHEL 6
    based systems. Existing certbot-auto installations affected by this will
    continue to work, but they will no longer receive updates. To install a
    newer version of Certbot on these systems, you should update your OS.
  • Support for Python 3.4 in Certbot and its ACME library is deprecated and will be
    removed in the next release of Certbot. certbot-auto users on x86_64 systems running
    RHEL 6 or derivatives will be asked to enable Software Collections (SCL) repository
    so Python 3.6 can be installed. certbot-auto can enable the SCL repo for you on CentOS 6
    while users on other RHEL 6 based systems will be asked to do this manually.

More details about these changes can be found on our GitHub repo.

4 Likes
2

“systems running RHEL 6 or derivatives will be asked to enable Software Collections (SCL) repository
so Python 3.6 can be installed.”

Can you suggest how to do that, as I am drawing a blank.

3

Here is a good starting point: https://wiki.centos.org/AdditionalResources/Repositories/SCL . That page uses the term “cutting edge”. I prefer the term “(b)leading edge”.

On the other hand, there are alternative ACME clients with less dependency footprint you may want to use: https://letsencrypt.org/docs/client-options/

1 Like
4

I ended up building Python 3.6.9 from source, sym-linking that to be python3, and running certbot-auto in --no-bootstrap mode.
(I need to renew manually as the server is firewall filtered to a set of IP addresses, and DNS verification is done by hand)

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.