From: Patrick McHardy <kaber@trash.net>
To: lists@naasa.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.10 with IPSEC problems?
Date: Sun, 26 Dec 2004 19:42:54 +0100 [thread overview]
Message-ID: <41CF062E.5090407@trash.net> (raw)
In-Reply-To: <200412261915.26681.lists@naasa.net>
Joerg Platte wrote:
> Thanks for the fast reply. It solved my problem. Is this change somewhere
> documented? Where can I get this kind of information, if I have problems in
> the future with the kernel IPSEC implementation?
The change was discussed on netdev before it went in. The
old behaviour was a security problem, so this change, which
breaks tunnel setups without forward policies, had to be
made. This will hopefully not happen again, but if you have
problems with IPsec and suspect a kernel bug, write to
netdev@oss.sgi.com.
Regards
Patrick
prev parent reply other threads:[~2004-12-26 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 14:53 Kernel 2.6.10 with IPSEC problems? Joerg Platte
2004-12-26 15:39 ` Patrick McHardy
2004-12-26 18:15 ` Joerg Platte
2004-12-26 18:42 ` Patrick McHardy [this message]
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=41CF062E.5090407@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@naasa.net \
/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