|
Authored by: Wol on Sunday, May 12 2013 @ 03:47 PM EDT |
But doesn't work as well if you're trying to kill the partition table to
repartition the drive ...
(Or maybe it does, but I'd rather not feed random rubbish into my disk
manglement program :-)
Cheers,
Wol[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Sunday, May 12 2013 @ 04:01 PM EDT |
It can be made even more secure by using /dev/random, eleven times, and then if
you want, zero it out. But really, if you're concerned about this level of
security, you have other issues and might just want to smash the drive. For all
purposes not involving special forensic equipment (not programs, equipment), I
do believe /dev/zero is sufficient. [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Monday, May 13 2013 @ 12:35 PM EDT |
The original problem was not even about secure erase, you seem to have put those
words into the OP's mouth.
OP only noted that diskutil did not seem to allow
reliably erasing a drive's partition table to allow him to do a completely fresh
OS X install on it - i.e., not re-using the original GPT.
And if you're
really trying to do a secure erase, using /dev/random is not a very good
strategy, and you shouldn't be suggesting it to people.
(It's better than not
erasing a drive at all, but that's the best I can say about it.)
This Wikipedia page on "data
remanence"
seems like a good place for you to start learning more. [ Reply to This | Parent | # ]
|
|
|
|
|