public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fgont@si6networks.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv6: Honor all IPv6 PIO Valid Lifetime values
Date: Thu, 23 Apr 2020 12:29:53 -0700 (PDT)	[thread overview]
Message-ID: <20200423.122953.620712677247198855.davem@davemloft.net> (raw)
In-Reply-To: <20200419122457.GA971@archlinux-current.localdomain>

From: Fernando Gont <fgont@si6networks.com>
Date: Sun, 19 Apr 2020 09:24:57 -0300

> RFC4862 5.5.3 e) prevents received Router Advertisements from reducing
> the Valid Lifetime of configured addresses to less than two hours, thus
> preventing hosts from reacting to the information provided by a router
> that has positive knowledge that a prefix has become invalid.
> 
> This patch makes hosts honor all Valid Lifetime values, as per
> draft-gont-6man-slaac-renum-06, Section 4.2. This is meant to help
> mitigate the problem discussed in draft-ietf-v6ops-slaac-renum.
> 
> Note: Attacks aiming at disabling an advertised prefix via a Valid
> Lifetime of 0 are not really more harmful than other attacks
> that can be performed via forged RA messages, such as those
> aiming at completely disabling a next-hop router via an RA that
> advertises a Router Lifetime of 0, or performing a Denial of
> Service (DoS) attack by advertising illegitimate prefixes via
> forged PIOs.  In scenarios where RA-based attacks are of concern,
> proper mitigations such as RA-Guard [RFC6105] [RFC7113] should
> be implemented.
> 
> Signed-off-by: Fernando Gont <fgont@si6networks.com>

Applied, thank you.

      reply	other threads:[~2020-04-23 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 12:24 [PATCH net-next] ipv6: Honor all IPv6 PIO Valid Lifetime values Fernando Gont
2020-04-23 19:29 ` David Miller [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=20200423.122953.620712677247198855.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fgont@si6networks.com \
    --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