From: Fernando Gont <fernando@gont.com.ar>
To: hannes@stressinduktion.org
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Fwd: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
Date: Thu, 15 Aug 2013 03:28:41 -0300 [thread overview]
Message-ID: <520C7519.1010000@gont.com.ar> (raw)
In-Reply-To: <20130814230617.GA13066@order.stressinduktion.org>
Hi, Hannes,
Thanks so much for your timely response! -- Please find my comments
in-line...
On 08/14/2013 08:06 PM, Hannes Frederic Sowa wrote:
> On Wed, Aug 14, 2013 at 05:19:13AM -0300, Fernando Gont wrote:
>> Folks,
>>
>> FYI. -- this is an important piece when it comes to First Hop (i.e.,
>> "local link") Security.
>
> Thanks for the heads-up, Fernando!
>
> I sketched up a patch to protect the receiving side. I still don't know if I
> should make this behaviour default or configurable via a sysctl knob. I really
> don't want to break existing installations.
Make it the default behavior. If anything, provide a sysctl knob to
override it.
Note: In the specific case of NS/NA messages, it's impossible nowadays
to find them fragmented in a real network (we don't even have options
(other than padding) to make NS/NAs grow so large!).
> As an extra plus, we now discard packets with nested fragment headers at once.
> Those packets should never have been accepted.
Is that the "goto fail_hdr" part in your patch?
P.S.: What about RS/RA messages?
Cheers,
--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
next prev parent reply other threads:[~2013-08-15 6:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130813221321.AEA1AB1E003@rfc-editor.org>
2013-08-14 8:19 ` Fwd: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery Fernando Gont
2013-08-14 23:06 ` Hannes Frederic Sowa
2013-08-15 6:28 ` Fernando Gont [this message]
2013-08-15 10:04 ` Hannes Frederic Sowa
2013-08-15 10:14 ` Loganaden Velvindron
2013-08-15 10:25 ` Hannes Frederic Sowa
2013-08-18 20:52 ` Loganaden Velvindron
2013-08-22 5:39 ` Loganaden Velvindron
2013-08-31 5:22 ` Fernando Gont
[not found] ` <CAOp4FwSatwRtx_O4Aio4e0HmahxdwiY9JToc8E+1rMT9oCjLrA@mail.gmail.com>
2013-08-31 5:20 ` Fernando Gont
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=520C7519.1010000@gont.com.ar \
--to=fernando@gont.com.ar \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.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 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).