Secure Deleting Files in Linux? Overwriting files with bits to secure erase?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Secure Deleting Files in Linux? Overwriting files with bits to secure erase?
Is there an option on Linux other than shred that will overwrite data?
The shred command only works for specific files and not the entire contents of folders. Id rather have the option integrated in the shell so the options given as you actually right click a/multiple file/folders.
You need to pass the -i option to cp. It will prompt the user if file already existing in a destination directory so that file would be overwritten with confirmation: http://www.cyberciti.biz/faq/cp-copy...unix-examples/
You need to pass the -i option to cp. It will prompt the user if file already existing in a destination directory so that file would be overwritten with confirmation
The only thing the "-i" option does is prompt the user for confirmation before writing to an existing file. It does not otherwise affect the operation of cp. There is absolutly no assurance that the same data blocks previously allocated to the file will be written with the new data. The first thing that cp does with the file is open it with the O_WRONLY and O_TRUNC options, which will truncate the file to zero length, deallocating the blocks it was using. As data is written, blocks will be allocated to receive it, but not necessarily the same blocks. For some filesystems, the allocator might well pick the blocks that were just freed, but that is not assured.
The shred command, and others like it, attempt to overwrite the same blocks by opening the file without the O_TRUNC option, but even then not all filesystems will perform the writes to the same logical blocks. And for devices like SSDs and flash drives, even overwriting the same logical blocks will almost certainly not write to the same physical blocks on the device.
The only thing the "-i" option does is prompt the user for confirmation before writing to an existing file. It does not otherwise affect the operation of cp. There is absolutly no assurance that the same data blocks previously allocated to the file will be written with the new data. The first thing that cp does with the file is open it with the O_WRONLY and O_TRUNC options, which will truncate the file to zero length, deallocating the blocks it was using. As data is written, blocks will be allocated to receive it, but not necessarily the same blocks. For some filesystems, the allocator might well pick the blocks that were just freed, but that is not assured.
The shred command, and others like it, attempt to overwrite the same blocks by opening the file without the O_TRUNC option, but even then not all filesystems will perform the writes to the same logical blocks. And for devices like SSDs and flash drives, even overwriting the same logical blocks will almost certainly not write to the same physical blocks on the device.
In that case; what method of cmd practice gives assurance that overwrite will be a sucess?
You can make cp replace an existing file without confirmation. In fact, that's what it does by default unless you have "cp" aliased to "cp -i". There is nothing you can do to ensure that cp will securely overwrite the disk blocks used by an existing file.
You can make cp replace an existing file without confirmation. In fact, that's what it does by default unless you have "cp" aliased to "cp -i". There is nothing you can do to ensure that cp will securely overwrite the disk blocks used by an existing file.
i have liked the Debian "srm" for years
it builds on Fedora on rhel and is in the Opensuse base packages
Code:
srm --help
Usage: srm [OPTION]... [FILE]...
Overwrite and remove (unlink) the files.
-d, --directory ignored (for compatability with rm(1))
-f, --force ignore nonexistant files, never prompt
-i, --interactive prompt before any removal
-x, --one-file-system do not cross file system boundaries
-s, --simple overwrite with single pass using 0x00
-P, --openbsd overwrite with three passes like OpenBSD rm
-D, --dod overwrite with 7 US DoD compliant passes
-E, --doe overwrite with 3 US DoE compliant passes
-r, -R, --recursive remove the contents of directories
-v, --verbose explain what is being done
-h, --help display this help and exit
-V, --version display version information and exit
BUT!!! and it is a VERY BIG BUTT
modern file systems might not write the data to the exact same sector
however there is a work around " dd"
you use it to make one honking HUGE file in the partition using rand or zero
for the root " / " partition
Code:
su -
dd if=/dev/zero of=/BIG_FILE.bin
and use the mount point for other partitions
"of=/dev/hdc2/BIG_FILE.bin "
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.