safe-rm 0.9 - Changelog

What's new in safe-rm 0.9:

January 12th, 2013

· This release adds /lib32 and /lib64 to the default list of protected paths.

What's new in safe-rm 0.8:

October 15th, 2009

· 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.

What's new in safe-rm 0.7:

September 23rd, 2009

· Version 0.7 of safe-rm fixes a small untainting problem for people who have CDPATH defined in their environment. Others can safely skip this release and stick to version 0.6.

What's new in safe-rm 0.6:

May 22nd, 2009

· The new release of safe-rm, version 0.6, fixes a bug which 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.

· You can still use safe-rm to protect regular files and directories from accidental deletion using the rm command, but symbolic links will no longer be protected.

· 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.

What's new in safe-rm 0.5:

April 2nd, 2009

· In addition to protecting specific files and directories from accidental deletion, this release of safe-rm introduces support for wildcards in protected paths.
· Minor improvements were also made to the documentation and overall code quality.

What's new in safe-rm 0.4:

November 1st, 2008

· The main change in this release is a fix for a bug that was preventing the root directory from being added to the list of protected paths.
· Safe-rm is now able to protect you from the infamous "rm -rf /".

What's new in safe-rm 0.3:

September 9th, 2008

· This release fixes a bug which caused safe-rm to skip the full blacklist checks when dealing with certain files and directories in the working directory.
· Previously, unless the argument you passed to safe-rm contained a slash, it would not get the real (absolute) path of the file before checking against the blacklist.