From: Tom Vier <tmv@comcast.net>
To: reiserfs-list@namesys.com
Subject: Re: secure delete?
Date: Tue, 23 Mar 2004 21:36:12 -0500 [thread overview]
Message-ID: <20040324023612.GA3880@zero> (raw)
In-Reply-To: <4060AEB9.1030200@namesys.com>
someone on l-k recently suggested storing a unique key in the inode. then
only the inode needs to be wiped to render all data blocks (including
strays) meaningless. i don't know how it was suggested this would be
implimented, but i would suggest generating the key at chattr +s time,
reading the file, encrypting it, and writing it back. that of course could
leave stray data, which is why new files should inherit +s from the dir
they're in. (i don't know what the rules are about +s inheritance - maybe it
needs chmod g+s on the dir).
btw, i wrote a file wiper which does blk and char devs, and regular files.
shameless plug:
http://wipe.sf.net/
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
next prev parent reply other threads:[~2004-03-24 2:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 10:13 secure delete? Peter Foldiak
2004-03-19 11:01 ` Cami
[not found] ` <20040319110748.GA30491@chihiro.cern.ch>
2004-03-19 11:29 ` Hans Reiser
2004-03-19 11:51 ` Peter Foldiak
2004-03-19 16:04 ` Hubert Chan
2004-03-19 17:54 ` Bennett Todd
2004-03-20 23:45 ` The Amazing Dragon
2004-03-20 23:59 ` Andrew Clausen
2004-03-23 1:37 ` Jurgen Botz
2004-03-23 2:49 ` Valdis.Kletnieks
2004-03-23 6:22 ` Hans Reiser
2004-03-23 6:40 ` Hendrik Visage
2004-03-23 16:34 ` Jürgen Botz
2004-03-23 21:03 ` Jason Holt
2004-03-23 21:40 ` Hans Reiser
2004-03-24 2:36 ` Tom Vier [this message]
2004-03-24 6:26 ` Jason Holt
2004-03-24 7:39 ` Hans Reiser
2004-03-24 15:38 ` Jason Holt
2004-03-29 12:59 ` Hans Reiser
2004-03-24 7:54 ` Hans Reiser
2004-03-24 8:04 ` Vladimir Saveliev
2004-03-24 23:18 ` Enrique Perez-Terron
2004-03-25 3:49 ` Tom Vier
2004-03-25 13:00 ` Vladimir Saveliev
2004-03-24 18:20 ` Valdis.Kletnieks
2004-03-25 3:16 ` Tom Vier
2004-03-30 1:10 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 2:13 Burnes, James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040324023612.GA3880@zero \
--to=tmv@comcast.net \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.