From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: ct: check return code from nla_parse_tested
Date: Thu, 20 Jun 2013 11:45:00 +0200 [thread overview]
Message-ID: <20130620094500.GA6225@localhost> (raw)
In-Reply-To: <1371052491-23863-1-git-send-email-dborkman@redhat.com>
On Wed, Jun 12, 2013 at 05:54:51PM +0200, Daniel Borkmann wrote:
> These are the only calls under net/ that do not check nla_parse_nested()
> for its error code, but simply continue execution. If parsing of netlink
> attributes fails, we should return with an error instead of continuing.
> In nearly all of these calls we have a policy attached, that is being
> type verified during nla_parse_nested(), which we would miss checking
> for otherwise.
Applied, thanks Daniel.
I'm going to run some tests, this may uncover wrong policies as they
were not enforced.
next prev parent reply other threads:[~2013-06-20 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 15:54 [PATCH nf-next] netfilter: ct: check return code from nla_parse_tested Daniel Borkmann
2013-06-20 9:45 ` Pablo Neira Ayuso [this message]
2013-06-20 9:47 ` Daniel Borkmann
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=20130620094500.GA6225@localhost \
--to=pablo@netfilter.org \
--cc=dborkman@redhat.com \
--cc=netfilter-devel@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).