Text of peps.python.org › pep-0644 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PEP 644 – Require OpenSSL 1.1.1 or newer | peps.python.org

PEP 644 – Require OpenSSL 1.1.1 or newer PEP 644 – Require OpenSSL 1.1.1 or newer Author : Christian Heimes <christian at python.org> Discussions-To : Discourse thread Status : Final Type : Standards Track Created : 27-Oct-2020 Python-Version : 3.10 Post-History : 27-Oct-2020, 03-Mar-2021, 17-Mar-2021, 17-Apr-2021 Resolution : Python-Dev message Table of Contents Abstract Motivation Impact OpenSSL 1.0.2 LTS OpenSSL 1.1.0 OpenSSL 1.1.1 LTS OpenSSL 3.0.0 LibreSSL BoringSSL Benefits TLS 1.3 Thread and fork safety SHA-3 Compatibility OpenSSL downstream patches and options LibreSSL support BoringSSL Rejected Ideas Formalize supported OpenSSL versions Keep support for OpenSSL 1.1.0 Backwards Compatibility Disclaimer and special thanks References Copyright Abstract This PEP proposes for CPython’s standard library to support only OpenSSL 1.1.1 LTS or newer.

Support for OpenSSL versions past end-of-lifetime, incompatible forks, and other TLS libraries are dropped. Motivation Python makes use of OpenSSL in hashlib , hmac , and ssl modules. OpenSSL provides fast implementations of cryptographic primitives and a full TLS stack including handling of X.509 certificates. The ssl module is used by standard library modules like urllib and 3rd party modules like urllib3 to implement secure variants of internet protocols. pip uses the ssl module to securely download packages from PyPI.

Any bug in the ssl module’s bindings to OpenSSL can lead to a severe security issue. Over time OpenSSL’s public API has evolved and changed. Version 1.0.2 introduced new APIs to verify and match hostnames. OpenSSL 1.1.0 made internal structs opaque and introduced new APIs that replace direct access of struct members. Version 3.0.0 will deprecate more APIs due to internal reorganization that moves cryptographic algorithms out of the core and into providers.

Forks like LibreSSL and BoringSSL have diverged in different directions. Currently Python versions 3.6 to 3.9 are compatible with OpenSSL 1.0.2, 1.1.0, and 1.1.1. For the most part Python also works with LibreSSL >= 2.7.1 with some missing features and broken tests. Due to limited resources and time it becomes increasingly hard to support multiple versions and forks as well as test and verify correctness. Besides multiple incompatible APIs there are build time flags, distribution-specific patches, and local crypto-policy settings that add to plethora of combinations.

On the other hand, the Python core team has only a couple of domain experts who are familiar with TLS and OpenSSL internals and even fewer who are active maintainers. Requiring OpenSSL 1.1.1 would allow us to give the vast majority of users a better experience, reduce our maintenance overhead and thus free resources to implement new features. Users would be able to rely on the presence of new features and consistent behavior, ultimately resulting in a more robust experience.

Impact OpenSSL 1.1.1 is the default variant and version of OpenSSL on almost all supported platforms and distributions. It’s also the only version that still receives security support from upstream [9] . No macOS and Windows user will be affected by the deprecation. The python.org installer and alternative distributions like Conda ship with most recent OpenSSL version. As of October 2020 and according to DistroWatch [1] most current BSD and Linux distributions ship with OpenSSL 1.1.1 as well.

Some older releases of long-term support (LTS) and enterprise distributions have older versions of OpenSSL or LibreSSL. By the time Python 3.10 will be generally available, several of these distributions will have reached end of lifetime, end of general support, or moved from LibreSSL to OpenSSL. Other software has dropped support for OpenSSL 1.0.2 as well. For example, PyCA cryptography 3.2 (2020-10-25) removed compatibility with OpenSSL 1.0.2.

OpenSSL 1.0.2 LTS released: 2015-02 end of lifetime: 2019-12 OpenSSL 1.0.2 added hostname verification, ALPN support, and elliptic curves. CentOS 7 (EOL 2024-06) Debian 8 Jessie (EOL 2020-07) Linux Mint 18.3 (EOL 2021-04) RHEL 7 (full support ends 2019-08, maintenance 2 support ends 2024-06) SUSE Enterprise Linux 12-SP5 (general supports ends 2024-10) Ubuntu 16.04 LTS / Xenial (general support ends 2021-04) OpenSSL 1.1.0 released: 2016-08 end of lifetime: 2019-09 OpenSSL 1.1.0 removed or disabled insecure ciphers by default and added support for ChaCha20-Poly1305, BLAKE2 (basic features), X25519 and CT.

The majority of structs were made opaque and new APIs were introduced. OpenSSL 1.1.0 is not API compatible with 1.0.2. Debian 9 Stretch (security support ended 2020-07, LTS until 2022-06) Ubuntu 18.04 LTS / Bionic (general support ends 2023-04) OpenSSL 1.1.1 LTS released: 2018-08 end of lifetime: 2023-09 (planned) OpenSSL 1.1.1 added TLS 1.3, SHA-3, X448 and Ed448. Alpine (switched back to OpenSSL in 2018 [4] ) Arch Linux current CentOS 8.0+ Debian 10 Buster Debian 11 Bullseye (ETA 2021-06) Fedora 29+ FreeBSD 11.3+ Gentoo Linux stable (dropped LibreSSL as alternative in January 2021 [10] ) HardenedBSD (switched back to OpenSSL in 2018 [3] ) Linux Mint 19.3+ macOS (python.org installer) NetBSD 8.2+ openSUSE 15.2+ RHEL 8.0+ Slackware current SUSE Enterprise Linux 15-SP2 Ubuntu 18.10+ Ubuntu 20.04 LTS / Focal VoidLinux (switched back to OpenSSL in March 2021 [5] ) Windows (python.org installer, Conda) Major CI providers provide images with OpenSSL 1.1.1.

AppVeyor (with image Ubuntu2004 ) CircleCI (with recent cimg/base:stable or cimg/base:stable-20.04 ) GitHub Actions (with runs-on: ubuntu-20.04 ) Giblab CI (with Debian Stretch, Ubuntu Focal, CentOS 8, RHEL 8, or Fedora runner) Packit TravisCI (with dist: focal ) Zuul OpenSSL 3.0.0 released: n/a (planned for mid/late 2021) OpenSSL 3.0.0 is currently under development. Major changes include relicensing to Apache License 2.0 and a new API for cryptographic algorithms providers.

Most changes are internal refactorings and don’t affect public APIs. [8] LibreSSL created: 2014-04 (forked from OpenSSL 1.0.1g) DragonFly BSD Hyperbola GNU/Linux-libre OpenBSD OpenELEC (discontinued) TrueOS (discontinued) Some distributions like FreeBSD and OPNsense also feature LibreSSL instead of OpenSSL as non-standard TLS libraries. Gentoo discontinued LibreSSL as an alternative to OpenSSL in January 2021 [10] due to compatibility issues and little testing.

OpenBSD ports has a port security/openssl/1.1 which is documented as “[…] is present to provide support for applications which cannot be made compatible with LibReSSL” [7] . The package could be used by OpenBSD to provide a working ssl module. BoringSSL created: 2014-06 BoringSSL is Google’s fork of OpenSSL. It’s not intended for general use and therefore not supported by Python. There are no guarantees of API or ABI stability.

Vendored copies of BoringSSL are used in Chrome/Chromium browser, Android, and on Apple platforms [6] . Benefits TLS 1.3 OpenSSL 1.1.1 introduced support for the new TLS 1.3 version. The latest version of the TLS protocol has a faster handshake and is more secure than the previous versions. Thread and fork safety Starting with release 1.1.0c, OpenSSL is fully fork and thread safe. Bindings no longer need any workarounds or additional callbacks to support multithreading.

SHA-3 Since 1.1.0, OpenSSL ships with SHA-3 and SHAKE implementations. Python’s builtin SHA-3 support is based on the reference implementation. The internal _sha3 code is fairly large and the resulting shared library close to 0.5 MB. Python could drop the builtin implementation and rely on OpenSSL’s libcrypto instead. So far LibreSSL upstream development has refused to add SHA-3 support. [2] Compatibility OpenSSL downstream patches and options OpenSSL features more than 70 configure and build time options in the form of OPENSSL_NO_* macros.

Around 60 options affect the presence of features like cryptographic algorithms and TLS versions. Some distributions apply patches to alter s

The rest of this page is on the live site.