From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <colinmca242@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 0/3] Disable OpenSSL and Python3-cryptography legacy features by default
Date: Thu, 12 Feb 2026 17:38:58 +0100 [thread overview]
Message-ID: <DGD4QO4N38MH.11MGPG2TIVUHJ@bootlin.com> (raw)
In-Reply-To: <20260211184917.1045939-1-colinmca242@gmail.com>
On Wed Feb 11, 2026 at 7:49 PM CET, Colin McAllister via lists.openembedded.org wrote:
> TLS 1.0 and 1.1 have been deprecated by the IETF since 2021, and
> OpenSSL's legacy module contains deprecated and unmaintained components.
> This series disables legacy support by default in both OpenSSL and
> python3-cryptography, requiring users to explicitly opt-in if needed.
>
> The first two patches add packageconfig options to control legacy TLS
> protocol support and the legacy OpenSSL module. The final patch aligns
> python3-cryptography with the new OpenSSL defaults.
>
> Note that the TLS 1.0/1.1 changes replace the existing "no-tls1" and
> "no-tls1_1" packageconfig options with affirmative "tls1" and "tls1_1"
> options that are disabled by default. While less disruptive to enable
> the "no-*" options by default, using affirmative options provides
> consistency with the new "legacy" option and is clearer than having
> default-enabled "no-*" options.
>
> Testing performed:
> * Verified both recipes build successfully with and without the new
> options
> * Ran OpenSSL ptests with legacy enabled/disabled and TLS 1.0/1.1
> disabled
> * Ran python3-cryptography ptests with legacy-openssl disabled
> * Confirmed ptests correctly skip tests for disabled legacy features
>
> Colin Pinnell McAllister (3):
> openssl: Disable TLS 1.x by default
> openssl: Add legacy packageconfig option
> python3-cryptography: Disable legacy-openssl by default
>
> meta/recipes-connectivity/openssl/openssl_3.5.5.bb | 14 +++++++++-----
> .../python/python3-cryptography.bb | 2 +-
> 2 files changed, 10 insertions(+), 6 deletions(-)
Hi Colin,
Thanks for your patch.
It looks like we are having some ptest failing on the autobuilder:
Failed ptests:
{'python3': ['test_min_max_version', 'python3']}
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/3075
https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/3030
Test logs can be found here:
https://valkyrie.yocto.io/pub/non-release/20260212-56/testresults/qemux86-64-ptest/core-image-ptest-python3/
https://valkyrie.yocto.io/pub/non-release/20260212-56/testresults/qemuarm64-ptest/core-image-ptest-python3/
Can you have a look at this error?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-02-12 16:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 18:49 [PATCH 0/3] Disable OpenSSL and Python3-cryptography legacy features by default Colin Pinnell McAllister
2026-02-11 18:49 ` [PATCH 1/3] openssl: Disable TLS 1.x " Colin Pinnell McAllister
2026-02-11 18:49 ` [PATCH 2/3] openssl: Add legacy packageconfig option Colin Pinnell McAllister
2026-02-13 18:23 ` [OE-core] " Peter Kjellerstedt
2026-02-11 18:49 ` [PATCH 3/3] python3-cryptography: Disable legacy-openssl by default Colin Pinnell McAllister
2026-02-12 16:38 ` Mathieu Dubois-Briand [this message]
2026-02-13 15:36 ` [OE-core] [PATCH 0/3] Disable OpenSSL and Python3-cryptography legacy features " Colin
2026-02-13 23:01 ` [PATCH v2 0/4] " Colin Pinnell McAllister
2026-02-13 23:01 ` [PATCH v2 1/4] python3: Backport TLS test fix Colin Pinnell McAllister
2026-02-13 23:01 ` [PATCH v2 2/4] openssl: Disable TLS 1.0/1.1 by default Colin Pinnell McAllister
2026-02-13 23:01 ` [PATCH v2 3/4] openssl: Add legacy packageconfig option Colin Pinnell McAllister
2026-02-13 23:01 ` [PATCH v2 4/4] python3-cryptography: Disable legacy-openssl by default Colin Pinnell McAllister
2026-02-15 16:43 ` [OE-core] [PATCH v2 0/4] Disable OpenSSL and Python3-cryptography legacy features " Mathieu Dubois-Briand
2026-02-15 18:03 ` Mathieu Dubois-Briand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DGD4QO4N38MH.11MGPG2TIVUHJ@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=colinmca242@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox