From: Patrick McHardy <kaber@trash.net>
To: Sven Anders <anders@anduras.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Status of Netfilter IPSEC patches
Date: Thu, 23 Jun 2005 17:06:22 +0200 [thread overview]
Message-ID: <42BACFEE.3020801@trash.net> (raw)
In-Reply-To: <42BACCD1.8030403@anduras.de>
Sven Anders wrote:
> | Patrick McHardy wrote:
> |
> | Read last weeks netdev archive, turns out the whole idea of skipping
> | netfilter hooks until all IPsec processing is done was wrong. I don't
> | know how to solve it yet.
>
> Any details about this?
> What problems can arise?
Raw sockets can have policies that allow them to receive packets
in intermediate states. Skipping the hooks on input until the
packet are entirely decrypted makes filtering before these sockets
impossible and is inconsistent with the way filtering can usually
be done.
It seems the only thing that would work is taking the opposite approach,
pass the packets through LOCAL_OUT/POST_ROUTING for each transform on
output and don't skip on input. For filtering in transport mode this
means we need to pass a packet through the stack for each transform on
input, not just for tunnel mode.
> I downloaded the latest patch-o-matic and looked at the state of the
> patches,
> but these are out-of-date. Are these patches unmaintained due to the
> statement
> above?
Yes.
> There are newer ones under:
> ~ http://www.saout.de/misc/linux-2.6.12-ipsec-nat/
> Please update the patches in the patch-o-matic!
If someone sends me a patch for svn I'll apply it.
Regards
Patrick
next prev parent reply other threads:[~2005-06-23 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 17:09 status of netfilter+ipsec patches Rolf Offermanns
2005-03-28 18:58 ` Tom Eastep
2005-03-28 19:49 ` Patrick McHardy
2005-03-29 8:55 ` Alexander Samad
2005-06-23 14:53 ` Status of Netfilter IPSEC patches Sven Anders
2005-06-23 15:06 ` Patrick McHardy [this message]
2005-06-27 8:14 ` Harald Welte
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=42BACFEE.3020801@trash.net \
--to=kaber@trash.net \
--cc=anders@anduras.de \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.