From: Akhil Goyal <gakhil@marvell.com>
To: Tejasree Kondoj <ktejasree@marvell.com>,
Radu Nicolau <radu.nicolau@intel.com>,
Declan Doherty <declan.doherty@intel.com>
Cc: Tejasree Kondoj <ktejasree@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Ciara Power <ciara.power@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Gagandeep Singh <g.singh@nxp.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
Archana Muniganti <marchana@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] security: add option to configure tunnel header verification
Date: Wed, 8 Sep 2021 10:42:51 +0000 [thread overview]
Message-ID: <CO6PR18MB44841A3FBBF99E7240A585A2D8D49@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210908082111.27396-2-ktejasree@marvell.com>
> Add option to indicate whether outer header verification
> need to be done as part of inbound IPsec processing.
>
> With inline IPsec processing, SA lookup would be happening
> in the Rx path of rte_ethdev. When rte_flow is configured to
> support more than one SA, SPI would be used to lookup SA.
> In such cases, additional verification would be required to
> ensure duplicate SPIs are not getting processed in the inline path.
>
> For lookaside cases, the same option can be used by application
> to offload tunnel verification to the PMD.
>
> These verifications would help in averting possible DoS attacks.
>
> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
> ---
> doc/guides/rel_notes/release_21_11.rst | 5 +++++
Deprecation notice should also be removed for this feature addition/
ABI breakage.
Other than that
Acked-by: Akhil Goyal <gakhil@marvell.com>
> lib/security/rte_security.h | 17 +++++++++++++++++
> 2 files changed, 22 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_21_11.rst
> b/doc/guides/rel_notes/release_21_11.rst
> index 0e3ed28378..b0606cb542 100644
> --- a/doc/guides/rel_notes/release_21_11.rst
> +++ b/doc/guides/rel_notes/release_21_11.rst
> @@ -136,6 +136,11 @@ ABI Changes
> soft and hard SA expiry limits. Limits can be either in units of packets or
> bytes.
>
> +* security: add IPsec SA option to configure tunnel header verification
> +
> + * Added SA option to indicate whether outer header verification need to
> be
> + done as part of inbound IPsec processing.
> +
>
> Known Issues
> ------------
> diff --git a/lib/security/rte_security.h b/lib/security/rte_security.h
> index 95c169d6cf..2a61cad885 100644
> --- a/lib/security/rte_security.h
> +++ b/lib/security/rte_security.h
> @@ -55,6 +55,14 @@ enum rte_security_ipsec_tunnel_type {
> /**< Outer header is IPv6 */
> };
>
> +/**
> + * IPSEC tunnel header verification mode
> + *
> + * Controls how outer IP header is verified in inbound.
> + */
> +#define RTE_SECURITY_IPSEC_TUNNEL_VERIFY_DST_ADDR 0x1
> +#define RTE_SECURITY_IPSEC_TUNNEL_VERIFY_SRC_DST_ADDR 0x2
> +
> /**
> * Security context for crypto/eth devices
> *
> @@ -195,6 +203,15 @@ struct rte_security_ipsec_sa_options {
> * by the PMD.
> */
> uint32_t iv_gen_disable : 1;
> +
> + /** Verify tunnel header in inbound
> + * * ``RTE_SECURITY_IPSEC_TUNNEL_VERIFY_DST_ADDR``: Verify
> destination
> + * IP address.
> + *
> + * * ``RTE_SECURITY_IPSEC_TUNNEL_VERIFY_SRC_DST_ADDR``: Verify
> both
> + * source and destination IP addresses.
> + */
> + uint32_t tunnel_hdr_verify : 2;
> };
>
> /** IPSec security association direction */
> --
> 2.27.0
next prev parent reply other threads:[~2021-09-08 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:21 [dpdk-dev] [PATCH 0/3] " Tejasree Kondoj
2021-09-08 8:21 ` [dpdk-dev] [PATCH 1/3] security: " Tejasree Kondoj
2021-09-08 7:46 ` Hemant Agrawal
2021-09-08 10:42 ` Akhil Goyal [this message]
2021-09-08 8:21 ` [dpdk-dev] [PATCH 2/3] common/cnxk: add support for " Tejasree Kondoj
2021-09-08 8:21 ` [dpdk-dev] [PATCH 3/3] test/crypto: add tunnel header verification tests Tejasree Kondoj
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=CO6PR18MB44841A3FBBF99E7240A585A2D8D49@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=adwivedi@marvell.com \
--cc=anoobj@marvell.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktejasree@marvell.com \
--cc=marchana@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=roy.fan.zhang@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;
as well as URLs for NNTP newsgroup(s).