Date: Tue, 24 Oct 2000 18:49:25 -0700 From: Kris Kennaway <kris@citusc.usc.edu> To: Eivind Eklund <eivind@FreeBSD.org> Cc: Kris Kennaway <kris@citusc.usc.edu>, Warner Losh <imp@village.org>, Mark Murray <mark@grondar.za>, arch@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <20001024184925.B59218@citusc17.usc.edu> In-Reply-To: <20001024182319.C37278@warning.follo.net>; from eivind@FreeBSD.org on Tue, Oct 24, 2000 at 06:23:19PM %2B0200 References: <20001024124057.A4309@skriver.dk> <200010232046.e9NKkLR01463@grimreaper.grondar.za> <20001023081548.A41843@bsdwins.com> <200010232046.e9NKkLR01463@grimreaper.grondar.za> <200010232321.RAA11268@harmony.village.org> <20001024124057.A4309@skriver.dk> <200010241256.GAA15067@harmony.village.org> <20001024162445.A58246@warning.follo.net> <20001024083111.D58506@citusc17.usc.edu> <20001024182319.C37278@warning.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 24, 2000 at 06:23:19PM +0200, Eivind Eklund wrote: > (Moving to -arch) > > On Tue, Oct 24, 2000 at 08:31:11AM -0700, Kris Kennaway wrote: > > On Tue, Oct 24, 2000 at 04:24:45PM +0200, Eivind Eklund wrote: > > > > > Can't we just crypt the data with a strong cipher (or, preferably, two or > > > three strong ciphers) and a key aquired by using random data from Yarrow > > > before writing it out? That would not expose state, assuming we trust the > > > > How would you know the key when you want to read it back in after the > > next reboot? > > You don't know the key. This is *entropy* - you don't need to recover it > exactly :-) This doesnt buy you anything, since the Yarrow algorithm already does this. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001024184925.B59218>