From: Greg KH <gregkh@linuxfoundation.org>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
stable@vger.kernel.org
Subject: Re: [PATCH 0/3] [-stable] Netfilter updates for stable 3.0 onwards
Date: Tue, 20 Nov 2012 11:31:46 -0800 [thread overview]
Message-ID: <20121120193146.GA9496@kroah.com> (raw)
In-Reply-To: <1353074415-21379-1-git-send-email-pablo@netfilter.org>
On Fri, Nov 16, 2012 at 03:00:11PM +0100, pablo@netfilter.org wrote:
> From: Pablo Neira Ayuso <pablo@netfilter.org>
>
> Hi!
>
> Please, consider the following Netfilter patches for stable 3.0 and
> onwards inclusion.
>
> The selected three patches are:
>
> 4a70bbf netfilter: Validate the sequence number of dataless ACK packets as well
> 64f509c netfilter: Mark SYN/ACK packets as invalid from original direction
> [BACKPORT] 38fe36a netfilter: nf_nat: don't check for port change on ICMP tuples
>
> The first two patches can be considered security fixes in the TCP connection
> tracking to make harder off-path attacks. For more information you can read:
> "Reflection scan: an Off-Path Attack on TCP" by Jan Wrobel.
>
> The latter fixes the re-routing of every ICMP packet going through NAT even
> if it is not required, which is an expensive operation. That one has been
> backported to 3.0.
>
> Please, cherry-pick them. Thanks!
All applied, thanks.
greg k-h
next prev parent reply other threads:[~2012-11-20 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 14:00 [PATCH 0/3] [-stable] Netfilter updates for stable 3.0 onwards pablo
2012-11-16 14:00 ` [PATCH 1/3] [-stable] netfilter: Mark SYN/ACK packets as invalid from original direction pablo
2012-11-16 14:00 ` [PATCH 2/3] [-stable] netfilter: Validate the sequence number of dataless ACK packets as well pablo
2012-11-16 14:00 ` [PATCH 3/3] [-stable] netfilter: nf_nat: don't check for port change on ICMP tuples pablo
2012-11-20 19:31 ` Greg KH [this message]
2012-11-25 13:59 ` [PATCH 0/3] [-stable] Netfilter updates for stable 3.0 onwards Ben Hutchings
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=20121120193146.GA9496@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=stable@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 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.