Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- #!/bin/bash
- # Author: Frash Pikass
- # Filename: distruggi
- #
- # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! CAUTION !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- # This is a potentially dangerous piece of code. Make sure to change owner to
- # root and make sure only root has execution permissions with
- #
- # sudo chown root distruggi
- # sudo chmod 744 distruggi
- #
- # to avoid accidental execution.
- #
- # This is based on shred, so the disclaimer in man shred is still valid:
- #
- # CAUTION: Note that shred relies on a very important assumption: that
- # the file system overwrites data in place. This is the traditional way
- # to do things, but many modern file system designs do not satisfy this
- # assumption. The following are examples of file systems on which shred
- # is not effective, or is not guaranteed to be effective in all file sys‐
- # tem modes:
- #
- # * log-structured or journaled file systems, such as those supplied with
- # AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)
- #
- # * file systems that write redundant data and carry on even if some
- # writes fail, such as RAID-based file systems
- #
- # * file systems that make snapshots, such as Network Appliance's NFS
- # server
- #
- # * file systems that cache in temporary locations, such as NFS version 3
- # clients
- #
- # * compressed file systems
- #
- # In the case of ext3 file systems, the above disclaimer applies (and
- # shred is thus of limited effectiveness) only in data=journal mode,
- # which journals file data in addition to just metadata. In both the
- # data=ordered (default) and data=writeback modes, shred works as usual.
- # Ext3 journaling modes can be changed by adding the data=something
- # option to the mount options for a particular file system in the
- # /etc/fstab file, as documented in the mount man page (man mount).
- #
- # 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.
- #
- # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! CAUTION !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- #
- # DESCRIPTION AND INSTRUCTIONS:
- # distruggi asks for permissions, asks for confirmation then permanently
- # deletes the argument file. It's optimized for integration with Thunar.
- # Launch with:
- # gksudo ./distruggi fileName filePath
- #
- # To add this as a custom action in Thunar, make sure the script distruggi is
- # in /usr/bin then follow the tutorial at
- # http://docs.xfce.org/xfce/thunar/custom-actions
- # Put this line in the command field:
- # gksudo /usr/bin/./distruggi %n %f
- # and make sure to check the right flags in the Appearance Conditions tab so
- # that file scheme is * and all boxes are checked except for Directories.
- zenity --question --title "Warning!" --text "Are you sure you want to permanently delete the file '$1'?" && test $? -eq 0 && (shred -n 200 -z -u "$2"; exit 0)
- # In Italian
- # zenity --question --title "Attenzione!" --text "Vuoi davvero cancellare il file '$1' in modo sicuro?" && test $? -eq 0 && (shred -n 200 -z -u "$2"; exit 0)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement