From: Stephan Mueller <stephan.mueller@atsec.com>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Andreas Dilger <aedilger@gmail.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"arnd@arndb.de" <arnd@arndb.de>, "Ted Ts'o" <tytso@mit.edu>,
jakub@redhat.com, drepper@redhat.com,
James Morris <james.l.morris@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] binfmt_elf.c: use get_random_int() to fix entropy depleting
Date: Thu, 07 Nov 2013 06:13:08 +0100 [thread overview]
Message-ID: <2161006.F8akiOkWYa@tauon> (raw)
In-Reply-To: <527B1399.8090805@oracle.com>
Am Donnerstag, 7. November 2013, 12:14:17 schrieb Jeff Liu:
Hi Jeff,
>Hi Stephan,
>
>As per your previous comments for this fix, you have promised another
>approach which is promising to avoid entropy starvation, I got this
>info from the following thread: [PATCH] avoid entropy starvation due
>to stack protection
>https://lkml.org/lkml/2012/12/14/267
There are several solutions:
- Ted is trying to prevent a constant reseeding of the nonblocking_pool
from the input_pool with a set of patches. I am unsure whether these
patches find their way into the kernel. With those patches, we can
happily keep get_random_bytes without too much strain on the input_pool
entropy -- i.e. drop the conversion to get_random_int.
- The begin of the email thread contains a patch that adds a new pool
which I called the kernel_pool that is just just for kernel internal
purposes. With Teds proposed changes to nonblocking_pool,
nonblocking_pool would behave almost like my kernel_pool and thus my
kernel_pool patch would not be needed.
- Lastly I am trying to add a new seed source to random.c and kernel
crypto API which could also be used as a stand-alone noise source. That
proposed noise source would effectively alleviate a lot of entropy
problems. The discussion for inclusion is raging at
http://lkml.org/lkml/2013/10/11/582. Ted is having concerns and we are
in a discussion to address those.
>
>My current fix has been merged into Andrew's tree(marked in "stuck"
>state) for a long time, and it also works well in our internal
>specific kernel, I'd like to know if there is any update from you, so
>that we can move it along for mainline. :)
>
>Thanks,
>-Jeff
Ciao
Stephan
next prev parent reply other threads:[~2013-11-07 5:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 4:12 [PATCH v4] binfmt_elf.c: use get_random_int() to fix entropy depleting Jeff Liu
2012-11-15 7:32 ` Kees Cook
2013-11-07 4:14 ` Jeff Liu
2013-11-07 4:53 ` Andrew Morton
2013-11-07 5:13 ` Stephan Mueller [this message]
2013-11-07 10:06 ` Jeff Liu
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=2161006.F8akiOkWYa@tauon \
--to=stephan.mueller@atsec.com \
--cc=aedilger@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=jeff.liu@oracle.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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.