pkgsrc changes:
- set LICENSE (x11)
- add test target
- add new NetBSD patches
- keep INTERIX patch, not tested
Upstream changelog
==================
release 1.2.15
fix handling of files > 2GB on Windows.
fix handling of symlinks to files owned by root.
release 1.2.14
fix fill() function, this fixes DoE and Gutmann modes.
new --rcmp mode.
use simple mode by default and not Gutmann 35 pass.
release 1.2.13
fix handling of OsX resource forks.
release-1_2_12
now using SVN on SourceForge.
small updates to autotools build files.
support Haiku operating system.
overwrite POSIX extended attributes.
srm has exit code != 0 if removing any file or directory failed.
handle alternate data streams on Windows and NTFS.
handle hard links on Windows and NTFS.
release-1_2_11
Win32 command line wildcard expansion
-v -v displays current write position
SIGINFO, SIGUSR2 display current write position
-x does not cross file system boundaries
overwrite block devices
release-1_2_10
Mac OsX compiles and works again
add DoE wipe mode
fix deletion of named pipes/fifos
Debian fixes
Win32 fixes
release-1_2_9
fix deletion of 0 byte files
fix handling of files <4096 bytes
fix handling of files >2GiB on 32bit
OpenBSD compat switch
handle OsX ressource fork
added some code from OsX port
Win32 version
by request on regional-fr.
Srm is a secure replacement for rm(1). Unlike the standard rm, it overwrites
the data in the target files before unlinkg them. This prevents command-line
recovery of the data by examining the raw block device. It may also help
frustrate physical examination of the disk, although it's unlikely that
completely protects against this type of recovery.
Srm uses algorithms found in _Secure Deletion of Data from Magnetic and
Solid-State Memory_ by Peter Gutmann and THC Secure Delete (the overwrite,
truncate, rename, unlink sequence).
All users, but especially Linux users, should be aware that srm will only
work on file systems that overwrite blocks in place. In particular, it will
_NOT_ work on resiserfs or the vast majority of journaled file systems. It
should work on ext2, FAT-based file systems, and the BSD native file system.
Ext3 users should be especially careful as it can be set to journal data as
well, which is an obvious route to reconstructing information.
