From: "David S. Miller" <davem@redhat.com>
To: Tom Lendacky <toml@us.ibm.com>
Cc: "Alexey N. Kuznetsov" <kuznet@ms2.inr.ac.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IPSec protocol application order
Date: 19 Feb 2003 17:32:09 -0800 [thread overview]
Message-ID: <1045704729.14999.2.camel@rth.ninka.net> (raw)
In-Reply-To: <OF67D9F550.2E100257-ON86256CD2.007CE0BF-86256CD2.007E9FBD@pok.ibm.com>
On Wed, 2003-02-19 at 15:03, Tom Lendacky wrote:
> I apologize if I missed it, but is there another way to set policy in the
> SPD besides the setkey command? I am under the assumption that setkey's
> spdadd operation is what is to be used to define the policy on the system
> so that racoon can perform dynamic keying.
That's correct.
But there is still no issue.
The user can make his machine non-RFC compliant by giving a bogus
specification to setkey. Kernel and setkey are merely doing what
the user asks of them.
This is akin to the user writing a RAW socket application which makes
the kernel output non-RFC compliant TCP packets. Do you suggest that
the kernel or some other part of the system should verify the packets
sent through the RAW socket interface? That is exactly what you are
telling us that setkey should be doing.
next prev parent reply other threads:[~2003-02-20 0:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 23:03 Tom Lendacky
2003-02-20 1:32 ` David S. Miller [this message]
2003-02-20 0:57 ` Chris Wedgwood
2003-02-20 6:51 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-02-20 14:40 Tom Lendacky
2003-02-19 21:48 Tom Lendacky
2003-02-19 21:39 ` David S. Miller
2003-02-19 22:07 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-19 20:42 Tom Lendacky
2003-02-19 21:29 ` Jeff Garzik
2003-02-19 21:20 ` David S. Miller
2003-02-19 22:05 ` David S. Miller
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=1045704729.14999.2.camel@rth.ninka.net \
--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
all inboxes | Powered by JetHome®