From: "Dan Anderson" <dtndan@cox.net>
To: <SELinux@tycho.nsa.gov>
Subject: Re: Linux Wipe Disk Utility
Date: Wed, 13 Aug 2003 18:50:14 -0500 [thread overview]
Message-ID: <00d901c361f5$a44cbc40$f800a8c0@cathy> (raw)
In-Reply-To: 200308131757.18235.joseph_a_nagy_jr@charter.net
----- Original Message -----
From: "Joseph A Nagy Jr" <joseph_a_nagy_jr@charter.net>
> Unless I'm mistaken, files on ext3 have their inodes automatically
> zeroed out upon file deletion. If this is the case, the above solutions
> are entirely unneccessary (at least the linux ones).
Inodes are not sufficient (unless ext3 is using really odd terminology,
inodes are essentially just collections of pointers to data blocks), you
need to wipe all of the data blocks, as I recall 3x, once with all 1's, once
with all 0's and once random (or a char and it's complement, and then
random).
My initial thought would be to use dd and /dev/zero, and /dev/random or
something along these lines (although, this would probably not be 100%
(blocks marked bad, and the alternate pool wouls also probably need wiped)).
We used to keep bootable floppies with "flush" on them for this purpose.
Which might suite your needs also.
Dan Anderson
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-08-13 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 22:07 Linux Wipe Disk Utility Tomás Palmer
2003-08-13 22:57 ` Joseph A Nagy Jr
2003-08-13 23:45 ` Russell Coker
2003-08-13 23:50 ` Dan Anderson [this message]
2003-08-14 0:03 ` OT: " James Griffin
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 19:29 Lugg William H Civ OO-ALC /MASFE
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='00d901c361f5$a44cbc40$f800a8c0@cathy' \
--to=dtndan@cox.net \
--cc=SELinux@tycho.nsa.gov \
/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.