Date: Thu, 26 Oct 2000 13:47:40 -0700 (PDT) From: Matt Dillon <dillon@earth.backplane.com> To: Mark Murray <mark@grondar.za> Cc: Doug Barton <DougB@gorean.org>, current@FreeBSD.ORG Subject: Re: entropy reseeding is totally broken Message-ID: <200010262047.e9QKleY45974@earth.backplane.com> References: <Pine.BSF.4.21.0010261218110.15371-100000@dt051n37.san.rr.com> <200010262029.e9QKTXM00442@grimreaper.grondar.za>
next in thread | previous in thread | raw e-mail | index | archive | help
:I like that, but I'd like to see more than one file. This avoids the race :where fsck may blat an incompletely written file after a (in)convenient :crash. : :We are really headed towards saving state in the first swap partition :(if there is one). :M :-- :Mark Murray :Join the anti-SPAM movement: http://www.cauce.org This would be trivial, you can use the swap allocation code (example: see the VN device, dev/vn/vn.c) to reserve, read, and write the swap. However, I don't see much of a point in doing this. Not everyone configures swap, so you can't count on it, and a system dump will overwrite swap, so you would have to mess around with that as well and I can tell you it just isn't worth the effort. Maintaining an entropy file in /var/db has no downside at all and is a whole lot easier to manage. This /dev/random stuff is a little wild -- I think the premis is sound, but you really need to look towards implementing more straightforward solutions rather then hacking up unrelated parts of the system. Forget doing special magic in the kernel. Forget using swap. Forget having ridiculously huge entropy files. Simplify it and everyone will be a whole lot happier. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010262047.e9QKleY45974>