From: John McNamara <john.mcnamara@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] [PATCH v1] doc: add note about patching third party dependencies
Date: Tue, 30 Jul 2019 12:07:55 +0100 [thread overview]
Message-ID: <1564484875-75300-1-git-send-email-john.mcnamara@intel.com> (raw)
Added a note to the getting started guides about patching third
party libraries/dependencies to avoid any known vulnerabilities.
Signed-off-by: John McNamara <john.mcnamara@intel.com>
---
doc/guides/freebsd_gsg/install_from_ports.rst | 6 ++++++
doc/guides/linux_gsg/sys_reqs.rst | 5 +++++
2 files changed, 11 insertions(+)
diff --git a/doc/guides/freebsd_gsg/install_from_ports.rst b/doc/guides/freebsd_gsg/install_from_ports.rst
index 633699e..baead28 100644
--- a/doc/guides/freebsd_gsg/install_from_ports.rst
+++ b/doc/guides/freebsd_gsg/install_from_ports.rst
@@ -46,6 +46,12 @@ those below would be added to the file ``/boot/loader.conf``.
hw.nic_uio.bdfs="2:0:0,2:0:1"
nic_uio_load="YES"
+.. note::
+
+ Please ensure that the latest patches are applied any third party libraries
+ or software to avoid any known vulnerabilities.
+
+
Compiling and Running the Example Applications
----------------------------------------------
diff --git a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst
index 10b01e3..d235905 100644
--- a/doc/guides/linux_gsg/sys_reqs.rst
+++ b/doc/guides/linux_gsg/sys_reqs.rst
@@ -81,6 +81,11 @@ Compilation of the DPDK
* Python, version 2.7+ or 3.2+, to use various helper scripts included in the DPDK package.
+.. note::
+
+ Please ensure that the latest patches are applied to third party libraries
+ and software to avoid any known vulnerabilities.
+
**Optional Tools:**
--
2.7.5
next reply other threads:[~2019-07-30 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 11:07 John McNamara [this message]
2019-08-06 21:45 ` 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=1564484875-75300-1-git-send-email-john.mcnamara@intel.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).