Re: Destructive Windows Script

Grant Edwards <[EMAIL PROTECTED]> writes: > > I take this to mean the the drive is non-functional and might > > have well been melted, except that demagnetising is cheaper. > > Yup. In a frequently cited scary paper (on the web &c.), Peter Gutmann claims claims that's not true in practise, IIRC:

Re: Destructive Windows Script

Magnus Lycka <[EMAIL PROTECTED]> wrote: >rbt wrote: >> data = ['0', 'a', '1', 'b', '2', 'c',\ >> '3', 'd', '4', 'e', '5', 'f',\ >> '6', 'g', '7', 'h', '8', 'i',\ >> '9', 'j', '~', '!', '@', '#',\ >> '$', '%

Re: Destructive Windows Script

rbt wrote: > data = ['0', 'a', '1', 'b', '2', 'c',\ > '3', 'd', '4', 'e', '5', 'f',\ > '6', 'g', '7', 'h', '8', 'i',\ > '9', 'j', '~', '!', '@', '#',\ > '$', '%', '^', '&', '*', ';'] > Note that the backsl

Re: Destructive Windows Script

rbt <[EMAIL PROTECTED]> writes: > Mike Meyer wrote: >> "Terry Reedy" <[EMAIL PROTECTED]> writes: >> >>> On *nix, one could open '/dev/rawdisk' (actual name depends on the >>> *nix build) and write a tracks worth of garbage for as many tracks >>> as there are. I don't how to programmaticly get the

Re: Destructive Windows Script

On 2005-06-06, rbt <[EMAIL PROTECTED]> wrote: >> Just open the raw disk device (assuming your Unix has such), >> and start writing data to it. Keep going until the write fails >> at the end of the media. > > Wouldn't /dev/urandom or /dev/random on Linux systems work > better? Maybe. Last time I

Re: Destructive Windows Script

Mike Meyer wrote: > "Terry Reedy" <[EMAIL PROTECTED]> writes: > >>On *nix, one could open '/dev/rawdisk' (actual name depends on the *nix >>build) and write a tracks worth of garbage for as many tracks as there are. >>I don't how to programmaticly get the track size and number (if there is a >>

Re: Destructive Windows Script

"Terry Reedy" <[EMAIL PROTECTED]> writes: > On *nix, one could open '/dev/rawdisk' (actual name depends on the *nix > build) and write a tracks worth of garbage for as many tracks as there are. > I don't how to programmaticly get the track size and number (if there is a > standard way at all).

Re: Destructive Windows Script

Terry Reedy wrote: > "Dennis Lee Bieber" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > >>My previous facility didn't even accept mil-spec wipes -- all >>disk drives leaving the facility had to go through a demagnitizer, > > > OT but I am curious: does a metallic case act as a

Re: Destructive Windows Script

On 2005-06-06, Terry Reedy <[EMAIL PROTECTED]> wrote: > OT but I am curious: does a metallic case act as a metallic shield, It depends on the metal and the case thickness. Thin sheet-aluminum provides virtually no magnetic shielding. Some good thick iron plate will provide shielding. > so that

Re: Destructive Windows Script

"Dennis Lee Bieber" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > My previous facility didn't even accept mil-spec wipes -- all > disk drives leaving the facility had to go through a demagnitizer, OT but I am curious: does a metallic case act as a metallic shield, so that the ca

Re: Destructive Windows Script

Michele Simionato wrote: > The problem is that Google gives me too many non-relevant hits. google("fat undelete") google("ext2 undelete") -- Robert Kern [EMAIL PROTECTED] "In the fields of hell where the grass grows high Are the graves of dreams allowed to die." -- Richard Harter -- http

Re: Destructive Windows Script

The problem is that Google gives me too many non-relevant hits. I just would like something like this: $ rm what-I-think-is-an-useless-file ACK! It was not that useless!! $ recover what-I-think-is-an-useless-file Michele Simionato -- http://mail.python.org/mailman/listinfo/py

Re: Destructive Windows Script

Michele Simionato wrote: > BTW, since this is a bit off-topic anyway, how do I recover > files accidentally removed? Is there a free tool that works > on FAT/NTFS and ext2/ext3? On all of those filesystems at the same time? Probably not. But there are tools for each. Google, and ye shall find. -

Re: Destructive Windows Script

On 05 Jun 2005 21:14:37 -0700, rumours say that Paul Rubin might have written: >The only way to be 100% sure the data is gone from a drive, is >basically to melt the drive. However, if your data is that sensitive, >you shouldn't ever write it to a hard drive in the clea

Re: Destructive Windows Script

BTW, since this is a bit off-topic anyway, how do I recover files accidentally removed? Is there a free tool that works on FAT/NTFS and ext2/ext3? Thanks, Michele Simionato -- http://mail.python.org/mailman/listinfo/python-list

Re: Destructive Windows Script

rbt <[EMAIL PROTECTED]> writes: > Thanks for the opinion... I don't do malware. Just interested in > speeding up file wiping (if possible) for old computers that will be > auctioned. The boot programs that you allude to (killdisk, autoclave) > work well, but are slow and tedious. Yes, you have to

Re: Destructive Windows Script

"Chris Lambacher" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > The reason they are slow and tedious is that they need to write to > every byte on the disk. Depending on the size of the disk, there may > be a lot of data that needs to be written, and if they are older > computers

Re: Destructive Windows Script

rbt wrote: > Chris Lambacher wrote: > >> The reason they are slow and tedious is that they need to write to >> every byte on the disk. Depending on the size of the disk, there may >> be a lot of data that needs to be written, and if they are older >> computers, write speed may not be particularly

Re: Destructive Windows Script

rbt wrote: > Chris Lambacher wrote: > >>The reason they are slow and tedious is that they need to write to >>every byte on the disk. Depending on the size of the disk, there may >>be a lot of data that needs to be written, and if they are older >>computers, write speed may not be particularly fas

Re: Destructive Windows Script

Chris Lambacher wrote: > The reason they are slow and tedious is that they need to write to > every byte on the disk. Depending on the size of the disk, there may > be a lot of data that needs to be written, and if they are older > computers, write speed may not be particularly fast. OK, I accept

Re: Destructive Windows Script

The reason they are slow and tedious is that they need to write to every byte on the disk. Depending on the size of the disk, there may be a lot of data that needs to be written, and if they are older computers, write speed may not be particularly fast. -Chris On 6/5/05, rbt <[EMAIL PROTECTED]>

Re: Destructive Windows Script

Roose wrote: > My guess would be: extremely, extremely easy. Since you're only writing 30 > bytes for each file, the vast majority of the data will still be present on > disk, just temporarily inaccessible because of the del command. And more > than likely it will be possible to recover 100% i

Re: Destructive Windows Script

My guess would be: extremely, extremely easy. Since you're only writing 30 bytes for each file, the vast majority of the data will still be present on disk, just temporarily inaccessible because of the del command. And more than likely it will be possible to recover 100% if they are using a j

Destructive Windows Script

How easy or difficult would it be for a computer forensics expert to recover data that is overwritten in this manner? This is a bit off-topic for comp.lang.python, but I thought some here would have some insight into this. Warning: **This code is destructive**. Do not run it unless you fully u