safe-rm is intended to prevent the accidental deletion of important files by replacing /bin/rm with a wrapper that checks the given arguments against a configurable blacklist of files and directories that should never be removed. Users who attempt to delete one of these protected files or directories will not be able to do so and will be shown a warning message instead. Protected paths can be set both at the site and user levels.
|Tags||Utilities safety delete protection delete prevention RM|
|Operating Systems||POSIX Linux|
This is an open invitation to all safe-rm users to send in their personal lists of protected paths so that some of these can hopefully be included in a future release. safe-rm is all about preventing little disasters and part of this involves shipping a default set of paths to protect from deletion. I've tried to guess what would be useful to people, but it's very likely that I have a missed a number of critical paths that people care about. So if you're happy with sharing your configuration, please consider emailing your /etc/safe-rm.conf or ~/.safe-rm to firstname.lastname@example.org.
Release Notes: This minor release adds IFS to the list of environment variables to untaint.
Release Notes: This version adds /lib32 and /lib64 to the default list of protected paths.
Release Notes: This new version removes an unnecessary dependency on the English Perl module. This makes safe-rm more robust during upgrades of the Perl core packages.
Release Notes: A small untainting problem was fixed for people who have CDPATH defined in their environment.
Release Notes: This release fixes a bug that caused symbolic links to protected files to be undeletable. Therefore, if you create a symlink to /usr/lib, you will now be able to delete it without having to use the real rm explicitly. Another minor enhancement included in this release is the change in the message displayed by safe-rm when a protected file is skipped. The new message should now make it explicit who is to blame when a file isn't being deleted.