Help using shred instead of rm Post: 302080310

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

BASH : Find files by date and shred them

Good afternoon everyone, For security reasons, I need to delete files on a HDD I have to send after the ending of a demo. I need to find all the files which not end by ".log" and which have been created for 45 days. After getting the file list, I would like to use the shred command. It...

2. UNIX for Dummies Questions & Answers

Shred utility

Hi experts. We have a HP-Unix server, we deleted some files and folders from the server. Is there any utilities that we can use to ensure those deleted files and folders are not recoverable? We used rm command to delete these files. Cheers, RT:confused:

3. UNIX for Advanced & Expert Users

shred multiple options

I've created a wxpython gui for the shred command. I can successfully mix and match all the shred options except two: -size and --random-source. (Man page definitions below). -size and --random-source seem to only work when they are used as the sole option passed. For example, I can zero a...

4. UNIX for Advanced & Expert Users

shred() not working on ext* file systems

When vfat format my128kb flash drive, shred works fine. But, when I format it using ext2 or ext3, shred() exits with this error: shred: /dev/sdb1: pass 1/1 (random)... shred: /dev/sdb1: error writing at offset 12288: Invalid argumentAnyone know what is going on?

5. BSD

Wipe out userland caches with shred, bleach bit is out of reach

Another topic that bothers me on bsd is the missing of bleach-bit. Looking at what bleach-bit can clean, the new version, it wipes out all the caches of the user. May someone can give me a hint how to clean the userland in bsd and all the hidden caches for the user. shred all rubbish or LSA cookies...

LEARN ABOUT REDHAT

shred

SHRED(1)								FSF								  SHRED(1)

NAME

       shred - delete a file securely, first overwriting it to hide its contents

SYNOPSIS

       shred [OPTIONS] FILE [...]

DESCRIPTION

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

       Mandatory arguments to long options are mandatory for short options too.

       -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
	      output 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, Ext3, 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

       In addition, file system backups and remote mirrors may contain copies of the file that cannot be removed, and that will allow  a  shredded
       file to be recovered later.

AUTHOR

       Written by Colin Plumb.

REPORTING BUGS

       Report bugs to <bug-coreutils@gnu.org>.

COPYRIGHT

       Copyright (C) 2002 Free Software Foundation, Inc.
       This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
       LAR PURPOSE.

SEE ALSO

       The full documentation for shred is maintained as a Texinfo manual.  If the info and shred programs are properly installed  at  your  site,
       the command

	      info shred

       should give you access to the complete manual.

shred (coreutils) 4.5.3 					   February 2003							  SHRED(1)