From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH next 1/2] net: netfilter: avoid get_random_bytes calls
Date: Fri, 20 Dec 2013 10:33:39 +0100 [thread overview]
Message-ID: <20131220093339.GA12971@localhost> (raw)
In-Reply-To: <1387473915-26753-1-git-send-email-fw@strlen.de>
On Thu, Dec 19, 2013 at 06:25:14PM +0100, Florian Westphal wrote:
> All these users need an initial seed value for jhash, prandom is
> perfectly fine. This avoids draining the entropy pool where
> its not strictly required.
>
> nfnetlink_log did not use the random value at all.
Applied, thanks Florian.
prev parent reply other threads:[~2013-12-20 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 17:25 [PATCH next 1/2] net: netfilter: avoid get_random_bytes calls Florian Westphal
2013-12-19 17:25 ` [PATCH next 2/2] netfilter: ctnetlink: honor CTA_MARK_MASK when setting ctmark Florian Westphal
2013-12-20 9:33 ` Pablo Neira Ayuso
2013-12-20 9:33 ` Pablo Neira Ayuso [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=20131220093339.GA12971@localhost \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--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).