Date: Tue, 22 Jul 2008 10:42:38 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Max Laier <max@love2party.net> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, "Andrey A. Chernov" <ache@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/lib/libc/gen arc4random.c Message-ID: <37752.1216723358@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 22 Jul 2008 12:39:57 %2B0200." <200807221239.57653.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200807221239.57653.max@love2party.net>, Max Laier writes: >On Tuesday 22 July 2008 12:34:51 Poul-Henning Kamp wrote: >> In message <200807221031.m6MAVe9I012301@repoman.freebsd.org>, "Andrey >> A. Cherno >> >> v" writes: >> > Increase initially dropped bytes from 512 to 768 (768 is also >> > suggested in the Ilya Mironov's article). 768 taken from another >> > research where it treats as default for RC4-drop(768): >> > http://www.users.zetnet.co.uk/hopwood/crypto/scan/cs.html#RC4-drop >> >> I've always wondered why the dropped number of bytes is constant, >> wouldn't it be smarter to drop a constant number, and then pull >> out the next byte and drop that many further bytes ? > >If you can observe the runtime that might give you a very good idea what >that byte was ... not sure if that is of relevance, but just a thought. Absolutely true but that would still be better than a fixed number wouldn't it ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37752.1216723358>