netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: Leon Romanovsky <leon@kernel.org>
Cc: Antony Antony <antony@phenome.org>,
	antony.antony@secunet.com,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	devel@linux-ipsec.org, Eyal Birger <eyal.birger@gmail.com>,
	Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [devel-ipsec] [PATCH ipsec-next v8] xfrm: Add Direction to the SA in or out
Date: Mon, 15 Apr 2024 11:36:15 +0200	[thread overview]
Message-ID: <Zhz1DmZZCrMq__B_@hog> (raw)
In-Reply-To: <20240414104500.GT4195@unreal>

2024-04-14, 13:45:00 +0300, Leon Romanovsky wrote:
> On Thu, Apr 11, 2024 at 10:00:07PM +0200, Sabrina Dubroca wrote:
> > 2024-04-11, 14:55:57 +0300, Leon Romanovsky wrote:
> > > On Thu, Apr 11, 2024 at 01:07:52PM +0200, Antony Antony via Devel wrote:
> > > > On Thu, Apr 11, 2024 at 01:37:40PM +0300, Leon Romanovsky via Devel wrote:
> > > > > On Tue, Apr 09, 2024 at 07:37:20PM +0200, Antony Antony via Devel wrote:
> > > > > > This patch introduces the 'dir' attribute, 'in' or 'out', to the
> > > > > > xfrm_state, SA, enhancing usability by delineating the scope of values
> > > > > > based on direction. An input SA will now exclusively encompass values
> > > > > > pertinent to input, effectively segregating them from output-related
> > > > > > values. This change aims to streamline the configuration process and
> > > > > > improve the overall clarity of SA attributes.
> > > > > > 
> > > > > > This feature sets the groundwork for future patches, including
> > > > > > the upcoming IP-TFS patch.
> > > > > > 
> > > > > > v7->v8:
> > > > > >  - add extra validation check on replay window and seq
> > > > > >  - XFRM_MSG_UPDSA old and new SA should match "dir"
> > > > > 
> > > > > Why? Update is add and delete operation, and one can update any field
> > > > > he/she wants, including direction.
> > > > 
> > > > Update operations are not strictly necessary without IKEv2. However, during
> > > > IKEv2 negotiation, updating "in" SA becomes essential.
> > > 
> > > The thing is if you want to limit update routine to fit IKEv2 only, or
> > > continue to allow users to do whatever they want with netlink and their
> > > own applications without *swan.
> > > 
> > > I don't have knowledge about such users, just remember seeking tons of
> > > guides how to setup IPsec tunnel with iproute2 and scripts, one of them
> > > can be potentially broken by this change.
> > 
> > Nothing is going to break with this change. Old scripts and old
> > userspace software are not providing XFRMA_SA_DIR, so none of the new
> > checks apply.
> 
> Right, but what about new iproute2, which eventually will users get
> after system update and old scripts?

I suspect that new iproute2 will add an option to set the direction
(otherwise it'd have to guess a value, that's not the goal of xfrm
support in iproute), and only pass XFRMA_SA_DIR when the user gave
that extra argument, so nothing will change there either?

-- 
Sabrina


  reply	other threads:[~2024-04-15  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 17:37 [PATCH ipsec-next v8] xfrm: Add Direction to the SA in or out Antony Antony
2024-04-11 10:37 ` [devel-ipsec] " Leon Romanovsky
2024-04-11 11:07   ` Antony Antony
2024-04-11 11:55     ` [devel-ipsec] " Leon Romanovsky
2024-04-11 20:00       ` Sabrina Dubroca
2024-04-14 10:45         ` Leon Romanovsky
2024-04-15  9:36           ` Sabrina Dubroca [this message]
2024-04-15 11:12             ` Christian Hopps
2024-04-15 18:12             ` Leon Romanovsky

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=Zhz1DmZZCrMq__B_@hog \
    --to=sd@queasysnail.net \
    --cc=antony.antony@secunet.com \
    --cc=antony@phenome.org \
    --cc=davem@davemloft.net \
    --cc=devel@linux-ipsec.org \
    --cc=edumazet@google.com \
    --cc=eyal.birger@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.com \
    --cc=steffen.klassert@secunet.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).