linux-kernel - Re: [PATCH] random: fix 32MB+ reads from /dev/urandom

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140809074841.GB1467@amd.pavel.ucw.cz>
Date:	Sat, 9 Aug 2014 09:48:41 +0200
From:	Pavel Machek <pavel@....cz>
To:	Theodore Ts'o <tytso@....edu>,
	Alexey Dobriyan <adobriyan@...il.com>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	acab@...italfuture.it, stable@...nel.org
Subject: Re: [PATCH] random: fix 32MB+ reads from /dev/urandom

On Wed 2014-07-23 16:26:41, Theodore Ts'o wrote:
> I don't think this patch is worthwhile.  There is no legitimate reason
> to be using such large reads like this, and read(2) is always allowed
> to return a short read (for example, if a signal comes in while the
> read is happening).  The only difference is that we are now guaranteed
> to return a short-read if you try to read more than 32MB.  Given

Regression from previous versions would be the reason. I'm pretty sure
someone has that dd in the scripts somewhere. (And signals are not an
issue in dd case.)
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/