Philipp Lehman wrote:
Ivo Wever [EMAIL PROTECTED] wrote:
Some people advise to repeat this procedure several times. Can anyone
explain why? I see no reason why one pass doesn't suffice.
[..]
http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html
Thanks for the replies and especially
hi ya philip
pick the method best for your paranoia level...
( more paranoia.. -- more time/$$$ to securely shred the disks
http://www.Linux-Sec.net/Txt/erase.txt
c ya
alvin
- 100% sure way...
take a hammer... and make itty=bitty pieces of the disks
and than burn it at high
On Thu, 13 Jun 2002 13:37:04 +0200, Philipp Lehman writes:
I want to sell an old machine that I don't use any more but there's
still sensitive stuff like personal emails, gpg keys, and passwords on
the hdd. What's the recommended way to securely 'shred' this data so
that it cannot be undeleted
I want to sell an old machine that I don't use any more but there's
still sensitive stuff like personal emails, gpg keys, and passwords on
the hdd. What's the recommended way to securely 'shred' this data so
that it cannot be undeleted by the next owner?
I assume I need to do something like
On Thu, Jun 13, 2002 at 01:37:04PM +0200, Philipp Lehman wrote:
I want to sell an old machine that I don't use any more but there's
still sensitive stuff like personal emails, gpg keys, and passwords on
the hdd. What's the recommended way to securely 'shred' this data so
that it cannot be
Robert Waldner wrote:
Philipp Lehman writes:
I want to sell an old machine that I don't use any more but there's
still sensitive stuff like personal emails, gpg keys, and passwords on
the hdd. What's the recommended way to securely 'shred' this data so
that it cannot be undeleted by the next
On Thu, 2002-06-13 at 13:54, Ivo Wever wrote:
But, for all practical values, a simple `dd if=dev/urandom bs=1M \
of=/dev/hdX` should be quite sufficient.
Some people advise to repeat this procedure several times. Can anyone
explain why? I see no reason why one pass doesn't suffice.
Data can
On Thu, Jun 13, 2002 at 02:54:44PM +0200, Ivo Wever wrote:
Robert Waldner wrote:
But, for all practical values, a simple `dd if=dev/urandom bs=1M \
of=/dev/hdX` should be quite sufficient.
Some people advise to repeat this procedure several times. Can anyone
explain why? I see no reason
I remember reading about a data recovery team that recovered
files after
the data had supposedly been removed with a 'dd' command like above.
www.ibas.no they claim to be able to see under 3 layers of overwrites. And
since they are a public contractor.. wonder what the not-so-public people
On Thursday 13 June 2002 14:54, Ivo Wever wrote:
Some people advise to repeat this procedure several times. Can anyone
explain why? I see no reason why one pass doesn't suffice.
IIRC, this has to do with minor mis-calibrations of the read/write heads
that may leave tiny traces of the old data
On 2002.06.13 09:16 Jan Johansson wrote:
I remember reading about a data recovery team that recovered
files after
the data had supposedly been removed with a 'dd' command like above.
www.ibas.no they claim to be able to see under 3 layers of overwrites.
And since they are a public
At 10:38 AM 6/13/2002 -0400, Ian D. Stewart wrote:
On 2002.06.13 09:16 Jan Johansson wrote:
I remember reading about a data recovery team that recovered
files after
the data had supposedly been removed with a 'dd' command like above.
www.ibas.no they claim to be able to see under 3 layers of
On Thu, Jun 13, 2002 at 12:21:33PM -0400, Loren Jordan wrote:
At 10:38 AM 6/13/2002 -0400, Ian D. Stewart wrote:
When I was in the (US) Navy, a hard drive that contained classified data
wasn't considered clean until after 7 swipes.
There are places that only consider a smoldering pile of
13 matches
Mail list logo
