From: Valdis.Kletnieks@vt.edu
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: Michel Lespinasse <walken@google.com>,
Theodore Ts'o <tytso@mit.edu>,
Artem Bityutskiy <dedekind1@gmail.com>,
netdev@vger.kernel.org, Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
devel@open-fcoe.org, akpm@linux-foundation.org,
Robert Love <robert.w.love@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
Eilon Greenstein <eilong@broadcom.com>
Subject: Re: [PATCH v2 00/11] introduce random32_get_bytes() and random32_get_bytes_state()
Date: Tue, 06 Nov 2012 00:14:32 -0500 [thread overview]
Message-ID: <90816.1352178872@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 04 Nov 2012 00:43:31 +0900." <1351957422-23243-1-git-send-email-akinobu.mita@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On Sun, 04 Nov 2012 00:43:31 +0900, Akinobu Mita said:
> This patchset introduces new functions into random32 library for
> getting the requested number of pseudo-random bytes.
>
> Before introducing these new functions into random32 library,
> prandom32() and prandom32_seed() with "prandom32" prefix are
> renamed to random32_state() and srandom32_state() respectively.
>
> The purpose of this renaming is to prevent some kernel developers
> from assuming that prandom32() and random32() might imply that only
> prandom32() was the one using a pseudo-random number generator by
> prandom32's "p", and the result may be a very embarassing security
> exposure.
Out of curiosity, why the '32'? I'm just waiting for some kernel developer to
do something stupid with this on a 64-bit arch because they think it's a 32-bit API. ;)
Should we bite the bullet and lose the 32, as long as we're churning the code *anyhow*?
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2012-11-06 5:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 15:43 [PATCH v2 00/11] introduce random32_get_bytes() and random32_get_bytes_state() Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 02/11] random32: " Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 04/11] mtd: nandsim: use random32_get_bytes Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 05/11] ubifs: " Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 06/11] mtd: mtd_nandecctest: use random32_get_bytes instead of get_random_bytes() Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 07/11] mtd: mtd_oobtest: convert to use random32_get_bytes_state() Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 08/11] mtd: mtd_pagetest: " Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 09/11] mtd: mtd_speedtest: use random32_get_bytes Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 10/11] mtd: mtd_subpagetest: convert to use random32_get_bytes_state() Akinobu Mita
2012-11-03 15:43 ` [PATCH v2 11/11] mtd: mtd_stresstest: use random32_get_bytes() Akinobu Mita
2012-11-06 5:14 ` Valdis.Kletnieks [this message]
2012-11-06 11:18 ` [PATCH v2 00/11] introduce random32_get_bytes() and random32_get_bytes_state() David Laight
2012-11-06 13:04 ` Akinobu Mita
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=90816.1352178872@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=adrian.hunter@intel.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dedekind1@gmail.com \
--cc=devel@open-fcoe.org \
--cc=dwmw2@infradead.org \
--cc=eilong@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=robert.w.love@intel.com \
--cc=tytso@mit.edu \
--cc=walken@google.com \
/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