linux-kernel - Re: [PATCH 8/9] random: tighten bound on random_read_wakeup

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 5 Dec 2013 19:31:28 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Greg Price <price@....EDU>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 8/9] random: tighten bound on random_read_wakeup_thresh

On Wed, Nov 13, 2013 at 03:08:35AM -0500, Greg Price wrote:
> We use this value in a few places other than its literal meaning,
> in particular in _xfer_secondary_pool() as a minimum number of
> bits to pull from the input pool at a time into either output
> pool.  It doesn't make sense to pull more bits than the whole size
> of an output pool.
> 
> We could and possibly should separate the quantities "how much
> should the input pool have to have to wake up /dev/random readers"
> and "how much should we transfer from the input to an output pool
> at a time", but nobody is likely to be sad they can't set the first
> quantity to more than 1024 bits, so for now just limit them both.
> 
> Cc: "Theodore Ts'o" <tytso@....edu>
> Signed-off-by: Greg Price <price@....edu>

Thanks, applied.

				- Ted
--
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/