From: "Ted Ts'o" <tytso@mit.edu>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: "random PID" - worth to be considered (again) ?
Date: Mon, 9 Jul 2012 12:17:22 -0400 [thread overview]
Message-ID: <20120709161722.GB7104@thunk.org> (raw)
In-Reply-To: <4FFAE24A.2070404@gmx.de>
On Mon, Jul 09, 2012 at 03:53:14PM +0200, Toralf Förster wrote:
> After reading [1] I'm wondering whether these would at least improve
> OpenSSL's implementation of a RSA key generator (page 13 in [1]) ?
Random PID's is a terribly way to get entropy into OpenSSL. You don't
get that many bits of entropy that way, and what bits of randomness
you get is coming from /dev/urandom. So improving the randomness of
/dev/urandom is what's important.
Regards,
- Ted
prev parent reply other threads:[~2012-07-09 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 13:53 Toralf Förster
2012-07-09 16:17 ` Ted Ts'o [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=20120709161722.GB7104@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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
Powered by JetHome