From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Securely deletion of an HDD
Date: Mon, 13 Jul 2015 12:54:56 +0200 [thread overview]
Message-ID: <20150713125456.61a4ee77@thetick> (raw)
In-Reply-To: <55A2D180.2030109@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
Am Sun, 12 Jul 2015 22:43:44 +0200
schrieb Volker Armin Hemmann <volkerarmin@googlemail.com>:
> http://www.howtogeek.com/115573/htg-explains-why-you-only-have-to-wipe-a-disk-once-to-erase-it/
Yeah, that was linked from the Arch wiki I looked at.
> http://www.vidarholen.net/~vidar/overwriting_hard_drive_data.pdf
FWIW, Peter Gutmann doesn't have much good to say about that article
(specifically, he wrote about the related blog article at [0] in his "Further
Epilogue" at [1]). Regardless, the summary still seems to be: with
modern high-density drives, there is *no* wiggle room outside for remnants of
data to stick around after overwriting it, outside of some potential future
method that is probably a) far enough away into the future that the data on the
drive is uninteresting by then (if it ever was interesting to begin with!) and
b) prohibitively expensive (at least at the start), which pushes the earliest
time someone might ever look at my old hard drives even further back. This
assumes that anybody is interested in developing something like that, if it's
even possible.
I can't help but wonder what the situation is like with tape, which still
commonly used for backups. ISTR that huge densities are also the norm there, but
that's about all I know.
[0]
https://web.archive.org/web/20090722235051/http://sansforensics.wordpress.com/2009/01/15/overwriting-hard-drive-data
[1] https://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-13 10:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 12:35 [gentoo-user] Securely deletion of an HDD Marc Joliet
2015-07-12 12:48 ` Rich Freeman
2015-07-12 14:39 ` Marc Joliet
2015-07-12 19:21 ` Rich Freeman
2015-07-12 19:42 ` Neil Bothwick
2015-07-13 15:03 ` [gentoo-user] " Grant Edwards
2015-07-13 17:20 ` Marc Joliet
2015-07-12 13:00 ` [gentoo-user] " Mick
2015-07-12 13:22 ` Francisco Ares
2015-07-12 16:32 ` Volker Armin Hemmann
2015-07-12 19:14 ` Rich Freeman
2015-07-12 20:43 ` Volker Armin Hemmann
2015-07-12 21:10 ` Rich Freeman
2015-07-12 21:20 ` Volker Armin Hemmann
2015-07-12 21:30 ` Rich Freeman
2015-07-13 8:05 ` Volker Armin Hemmann
2015-07-13 11:03 ` Rich Freeman
2015-07-12 22:22 ` R0b0t1
2015-07-13 0:18 ` Rich Freeman
2015-07-13 1:50 ` Thomas Mueller
2015-07-13 8:09 ` Volker Armin Hemmann
2015-07-13 10:58 ` Marc Joliet
2015-07-14 22:21 ` R0b0t1
2015-07-15 12:29 ` Rich Freeman
2015-07-13 10:54 ` Marc Joliet [this message]
2015-07-13 11:04 ` Marc Joliet
2015-07-13 9:53 ` Joerg Schilling
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=20150713125456.61a4ee77@thetick \
--to=marcec@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox