public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Emma Finn <emma.finn@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com, kai.ji@intel.com,
	Emma Finn <emma.finn@intel.com>
Subject: [PATCH] doc: deprecation of OpenSSL version 1.1.1
Date: Wed, 11 Feb 2026 12:19:16 +0000	[thread overview]
Message-ID: <20260211121916.2598788-1-emma.finn@intel.com> (raw)

OpenSSL 1.1.1 reached end-of-life in September 2023. Future
releases of DPDK will require minimum of OpenSSL 3.0.

Signed-off-by: Emma Finn <emma.finn@intel.com>
---
 doc/guides/rel_notes/deprecation.rst | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ac667e91a6..fca556d07b 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -20,6 +20,11 @@ Deprecation Notices
 * kvargs: The function ``rte_kvargs_process`` will get a new parameter
   for returning key match count. It will ease handling of no-match case.
 
+* cryptodev: Support for OpenSSL versions earlier than 3.0 is deprecated
+  and will be removed. OpenSSL 1.1.1 reached end-of-life in September 2023.
+  The minimum supported OpenSSL version will be 3.0,
+  and version checks for earlier OpenSSL versions will be removed from the PMD.
+
 * eal: The ``-c <coremask>`` commandline parameter is deprecated
   and will be removed in a future release.
   Use the ``-l <corelist>`` or ``--lcores=<corelist>`` parameters instead
-- 
2.43.0


             reply	other threads:[~2026-02-11 12:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11 12:19 Emma Finn [this message]
2026-02-17 14:40 ` [EXTERNAL] [PATCH] doc: deprecation of OpenSSL version 1.1.1 Akhil Goyal
2026-03-03 15:42   ` Ji, Kai
2026-03-06  3:39   ` Hemant Agrawal
2026-03-22 20:57   ` [EXTERNAL] " Jack Bond-Preston
2026-03-22 20:59     ` Jack Bond-Preston
2026-03-31 11:00 ` Thomas Monjalon

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=20260211121916.2598788-1-emma.finn@intel.com \
    --to=emma.finn@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.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