public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: toml@us.ibm.com
Cc: linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: IPSec: AH/ESP combination problems
Date: Wed, 12 Feb 2003 22:48:06 -0800 (PST)	[thread overview]
Message-ID: <20030212.224806.97357557.davem@redhat.com> (raw)
In-Reply-To: <3E4AD852.4060300@us.ibm.com>

   From: Tom Lendacky <toml@us.ibm.com>
   Date: Wed, 12 Feb 2003 17:27:14 -0600

   Again I'm not familiar enough with the code at this point
   to determine how to get the ESP protocol to be processed
   before the AH protocol in this case

You can enforce the ordering exactly when the xfrm templates
are built, this ensures that any fully resolved xfrm state
created from them have the correct ordering as well.

  reply	other threads:[~2003-02-13  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-12 23:27 IPSec: AH/ESP combination problems Tom Lendacky
2003-02-13  6:48 ` David S. Miller [this message]
2003-02-17 18:25 ` kuznet
  -- strict thread matches above, loose matches on Subject: below --
2003-02-13 21:28 Tom Lendacky

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=20030212.224806.97357557.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toml@us.ibm.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