DPDK patches and discussions
 help / color / mirror / Atom feed
From: John McNamara <john.mcnamara@intel.com>
To: declan.doherty@intel.com
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH v1] doc: add recommendation to update to latest openssl version
Date: Fri, 23 Oct 2020 16:20:28 +0000
Message-ID: <20201023162028.1619189-1-john.mcnamara@intel.com> (raw)

Add recommendation to update to latest OpenSSL version when
using the OpenSSL PMD and to at least version 1.1.1g to avoid
known CVEs.

Signed-off-by: John McNamara <john.mcnamara@intel.com>
 doc/guides/cryptodevs/openssl.rst | 24 +++++-------------------
 1 file changed, 5 insertions(+), 19 deletions(-)

diff --git a/doc/guides/cryptodevs/openssl.rst b/doc/guides/cryptodevs/openssl.rst
index ca0f0b43f..848a2e8eb 100644
--- a/doc/guides/cryptodevs/openssl.rst
+++ b/doc/guides/cryptodevs/openssl.rst
@@ -58,27 +58,13 @@ Supported Asymmetric Crypto algorithms:
-To compile openssl PMD, appropriate openssl packages have to be installed
-in the build environment.
+To compile the OpenSSL PMD the openssl library must be installed. It will
+then be picked up by the Meson/Ninja build system.
-The newest openssl library version is supported:
+To ensure that you have the latest security fixes it is recommended that you
+use version 1.1.1g or newer.
-* 1.0.2h-fips  3 May 2016.
-Older versions that were also verified:
-* 1.0.1f 6 Jan 2014
-* 1.0.1 14 Mar 2012
-For Ubuntu 14.04 LTS these packages have to be installed in the build system:
-.. code-block:: console
-    sudo apt-get install openssl
-    sudo apt-get install libc6-dev-i386 # for i686-native-linux-gcc target
-This code was also verified on Fedora 24.
-This code has NOT been verified on FreeBSD yet.
+* 1.1.1g, 2020-Apr-21. https://www.openssl.org/source/

             reply	other threads:[~2020-10-23 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 16:20 John McNamara [this message]
2020-10-28 11:55 ` Akhil Goyal

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201023162028.1619189-1-john.mcnamara@intel.com \
    --to=john.mcnamara@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git