[pkgsrc/trunk]: pkgsrc/security/srm Initial import of srm, version 1.2.8 into...

[cube <cube%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/91beeb40005b
branches:  trunk
changeset: 469845:91beeb40005b
user:      cube <cube%pkgsrc.org@localhost>
date:      Mon Mar 01 09:43:06 2004 +0000

description:
Initial import of srm, version 1.2.8 into the NetBSD Package Collection,
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.

diffstat:

 security/srm/DESCR    |  16 ++++++++++++++++
 security/srm/Makefile |  15 +++++++++++++++
 security/srm/PLIST    |   3 +++
 security/srm/distinfo |   4 ++++
 4 files changed, 38 insertions(+), 0 deletions(-)

diffs (54 lines):

diff -r b017b9d2afe0 -r 91beeb40005b security/srm/DESCR
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/security/srm/DESCR        Mon Mar 01 09:43:06 2004 +0000
@@ -0,0 +1,16 @@
+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.
diff -r b017b9d2afe0 -r 91beeb40005b security/srm/Makefile
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/security/srm/Makefile     Mon Mar 01 09:43:06 2004 +0000
@@ -0,0 +1,15 @@
+# $NetBSD: Makefile,v 1.1.1.1 2004/03/01 09:43:06 cube Exp $
+#
+
+DISTNAME=              srm-1.2.8
+CATEGORIES=            security
+MASTER_SITES=          ${MASTER_SITE_SOURCEFORGE:=srm/}
+
+MAINTAINER=            cube%NetBSD.org@localhost
+HOMEPAGE=              http://srm.sourceforge.net/
+COMMENT=               Secure replacement for rm(1)
+
+USE_BUILDLINK3=                yes
+GNU_CONFIGURE=         yes
+
+.include "../../mk/bsd.pkg.mk"
diff -r b017b9d2afe0 -r 91beeb40005b security/srm/PLIST
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/security/srm/PLIST        Mon Mar 01 09:43:06 2004 +0000
@@ -0,0 +1,3 @@
+@comment $NetBSD: PLIST,v 1.1.1.1 2004/03/01 09:43:06 cube Exp $
+bin/srm
+man/man1/srm.1
diff -r b017b9d2afe0 -r 91beeb40005b security/srm/distinfo
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/security/srm/distinfo     Mon Mar 01 09:43:06 2004 +0000
@@ -0,0 +1,4 @@
+$NetBSD: distinfo,v 1.1.1.1 2004/03/01 09:43:07 cube Exp $
+
+SHA1 (srm-1.2.8.tar.gz) = 8b7aafc95b3ef67e2c737030567222bf50082188
+Size (srm-1.2.8.tar.gz) = 88067 bytes