Date: Thu, 20 May 1999 11:33:04 +0400 (MSD) From: "Ilmar S. Habibulin" <ilmar@ints.ru> To: Warner Losh <imp@harmony.village.org> Cc: posix1e@cyrus.watson.org, freebsd-security@FreeBSD.ORG Subject: Re: secure deletion Message-ID: <Pine.BSF.4.05.9905201119560.19693-100000@ws-ilmar.ints.ru> In-Reply-To: <199905200624.AAA04145@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 May 1999, Warner Losh wrote: > There is a certain segment of the community that would use it. If > there was zero overhead (beyond a bit compare on unlink) when not > used, binary compatible with current disks and a fairly clean > implementation, then I think that there would be support for its > inclusion. My implementation was very simple. In order to secure ;-) delete file user have to set special flag (bit) of inode. I think, that i can use ufs flags field for that bit and chflags command. When i catch up situations of unlinking file, truncaing its size, i bzero unused blocks. While unlinking i found strange thing. I'm deleting blocks sequently from low blkno to high. If i change this sequence back to front (?) i've go no bzero'ed blocks at all. Maybe there is some other way of wiping blocks? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9905201119560.19693-100000>