Date: Tue, 24 Oct 2000 08:31:11 -0700 From: Kris Kennaway <kris@citusc.usc.edu> To: Eivind Eklund <eivind@FreeBSD.org> Cc: Warner Losh <imp@village.org>, Mark Murray <mark@grondar.za>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <20001024083111.D58506@citusc17.usc.edu> In-Reply-To: <20001024162445.A58246@warning.follo.net>; from eivind@FreeBSD.org on Tue, Oct 24, 2000 at 04:24:45PM %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>
next in thread | previous in thread | raw e-mail | index | archive | help
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? > I'd not like to write it to swap without encryption; I do not want access to > swap to help in recovering previous Yarrow state. It doesn't..it does by definition let you control what state it starts up in next time, but if you have write access to the physical disk you can do that anyway. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001024083111.D58506>