From: "Toralf Förster" <toralf.foerster@gmx.de>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: "random PID" - worth to be considered (again) ?
Date: Mon, 09 Jul 2012 15:53:14 +0200 [thread overview]
Message-ID: <4FFAE24A.2070404@gmx.de> (raw)
After reading [1] I'm wondering whether these would at least improve
OpenSSL's implementation of a RSA key generator (page 13 in [1]) ?
/me knows about the security-by-obscurity discussion like in [2],
however here I do not speak about guessing next PID, but about the
described entropy hole.
[1] https://factorable.net/weakkeys12.extended.pdf
[2] http://marc.info/?t=94754302700001&r=1&w=2
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next reply other threads:[~2012-07-09 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 13:53 Toralf Förster [this message]
2012-07-09 16:17 ` "random PID" - worth to be considered (again) ? Ted Ts'o
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=4FFAE24A.2070404@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.