PGP wipe utility?

[Propaganda]

Is PGP's wipe utility going to erase the contents from my harddrive permantely and untraceable. Lets say if the FBI got a hold of my comp and my temp and erased files are disk wiped more than 9 times, they cant recapture that data right?? Is ther another disk wipe utility that will allow me to wipe files that i choose thats better than PGP's?


My other question is what is anonimizer and diskcrypt4 and where can I find them at, i am willing to buy??

Last question, what does it mean when ur disk is mounted and how to u unmount or demount a drive?

thanx

[DeadAddict]

I believe there is really no one program that can totally wipe a drive someone some where will be able to extract some or all of the data unless you shatter the platters or bend them all to hell or you can use this http://www.hackology.com/programs/hdkp/ginfo.shtml

For anonimizer www.anonimizer.com will tell you all you need to know

Mounting and umounting a drive
The process of merging filesystems in this way is called mounting. When a device is mounted, it is then accessible to the system's users. The directory under which a mounted device's filesystem is accessible is known as the mount point. In the previous paragraph's example, /mnt/floppy was the diskette drive's mount point. Note that there are no restrictions (other than common conventions) on the naming of mount points. We could have just as easily mounted the floppy to /long/path/to/the/floppy/drive.
(Source linux man pages)

[99¢]

Usage: shred [OPTIONS] FILE [...]
Overwrite the specified FILE(s) repeatedly, in order to make it harder
for even very expensive hardware probing to recover the data.

-f, --force change permissions to allow writing if necessary
-n, --iterations=N Overwrite N times instead of the default (25)
-s, --size=N shred this many bytes (suffixes like k, M, G accepted)
-u, --remove truncate and remove file after overwriting
-v, --verbose show progress
-x, --exact do not round file sizes up to the next full block
-z, --zero add a final overwrite with zeros to hide shredding
- shred standard output
--help display this help and exit
--version print version information and exit

Delete FILE(s) if --remove (-u) is specified. The default is not to remove
the files because it is common to operate on device files like /dev/hda,
and those files usually should not be removed. When operating on regular
files, most people use the --remove option.

CAUTION: Note that shred relies on a very important assumption:
that the filesystem overwrites data in place. This is the traditional
way to do things, but many modern filesystem designs do not satisfy this
assumption. The following are examples of filesystems on which shred is
not effective:

* log-structured or journaled filesystems, such as those supplied with
AIX and Solaris (and JFS, ReiserFS, XFS, etc.)

* filesystems that write redundant data and carry on even if some writes
fail, such as RAID-based filesystems

* filesystems that make snapshots, such as Network Appliance's NFS server

* filesystems that cache in temporary locations, such as NFS
version 3 clients

* compressed filesystems

Report bugs to <[email protected]>.