From: "Yoann Congal" <yoann.congal@smile.fr>
To: <vanusuri@mvista.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][patch 2/3] python3-cryptography: Fix CVE-2026-69248
Date: Mon, 21 Sep 2026 17:44:22 +0200 [thread overview]
Message-ID: <DLL3Z9HE1TTX.36E2F147N6AS9@smile.fr> (raw)
In-Reply-To: <20260901092741.34198-2-vanusuri@mvista.com>
On Tue Sep 1, 2026 at 11:27 AM CEST, Vijay Anusuri via lists.openembedded.org wrote:
> Pick patch according to [2]
>
> [1] https://nvd.nist.gov/vuln/detail/cve-2026-69248
> [2] https://security-tracker.debian.org/tracker/CVE-2026-69248
>
> Signed-off-by: Vijay Anusuri <vanusuri@mvista.com>
> ---
> .../python3-cryptography/CVE-2026-69248.patch | 297 ++++++++++++++++++
> .../python/python3-cryptography_42.0.5.bb | 1 +
> 2 files changed, 298 insertions(+)
> create mode 100644 meta/recipes-devtools/python/python3-cryptography/CVE-2026-69248.patch
>
> diff --git a/meta/recipes-devtools/python/python3-cryptography/CVE-2026-69248.patch b/meta/recipes-devtools/python/python3-cryptography/CVE-2026-69248.patch
> new file mode 100644
> index 0000000000..5ccccd8034
> --- /dev/null
> +++ b/meta/recipes-devtools/python/python3-cryptography/CVE-2026-69248.patch
> @@ -0,0 +1,297 @@
> +From 4d035a4225965edeffd312079a510ef25fcfdcb2 Mon Sep 17 00:00:00 2001
> +From: William Woodruff <william@yossarian.net>
> +Date: Thu, 21 May 2026 20:44:05 -0400
> +Subject: [PATCH] x509: distinguish NC kinds when evaluating wildcard DNS SANs
> + (#14888)
> +
> +* x509: distinguish NC kinds when evaluating wildcard DNS SANs
> +
> +* Bump x509-limbo
> +
> +Upstream-Status: Backport [import from suse python-cryptography-42.0.4-slfo.1.1_6.1.src.rpm
Hello,
"suse python-cryptography-42.0.4-slfo.1.1_6.1.src.rpm": Where can I
download this? My usual Search engines/LLMs are not helpful here (and I
don't want to resort to boot a Suse container, yet)
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-09-21 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 9:27 [OE-core][scarthgap][patch 1/3] python3-cryptography: Fix CVE-2026-34073 Vijay Anusuri
2026-09-01 9:27 ` [OE-core][scarthgap][patch 2/3] python3-cryptography: Fix CVE-2026-69248 Vijay Anusuri
2026-09-10 14:20 ` Yoann Congal
2026-09-18 5:50 ` Vijay Anusuri
2026-09-18 8:20 ` Yoann Congal
2026-09-21 15:44 ` Yoann Congal [this message]
2026-09-21 16:26 ` Vijay Anusuri
2026-09-21 17:10 ` Yoann Congal
2026-09-01 9:27 ` [OE-core][scarthgap][patch 3/3] python3-cryptography: Fix CVE-2026-69249 Vijay Anusuri
2026-09-21 17:16 ` Yoann Congal
2026-09-22 6:25 ` Vijay Anusuri
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=DLL3Z9HE1TTX.36E2F147N6AS9@smile.fr \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=vanusuri@mvista.com \
/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