summaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorcube <cube@pkgsrc.org>2004-03-01 09:43:06 +0000
committercube <cube@pkgsrc.org>2004-03-01 09:43:06 +0000
commit24dcecdd5fe5c8df0725ca1fa5aa48dc0ea01cce (patch)
treef1b9db9d2d80da8f355fbe1b855d2c26197728a3 /security
parent658f3a6c64def6e6560a4d77fd12e20c4e692787 (diff)
downloadpkgsrc-24dcecdd5fe5c8df0725ca1fa5aa48dc0ea01cce.tar.gz
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 (limited to 'security')
-rw-r--r--security/srm/DESCR16
-rw-r--r--security/srm/Makefile15
-rw-r--r--security/srm/PLIST3
-rw-r--r--security/srm/distinfo4
4 files changed, 38 insertions, 0 deletions
diff --git a/security/srm/DESCR b/security/srm/DESCR
new file mode 100644
index 00000000000..eff0f282f0e
--- /dev/null
+++ b/security/srm/DESCR
@@ -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 --git a/security/srm/Makefile b/security/srm/Makefile
new file mode 100644
index 00000000000..c09b542257e
--- /dev/null
+++ b/security/srm/Makefile
@@ -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
+HOMEPAGE= http://srm.sourceforge.net/
+COMMENT= Secure replacement for rm(1)
+
+USE_BUILDLINK3= yes
+GNU_CONFIGURE= yes
+
+.include "../../mk/bsd.pkg.mk"
diff --git a/security/srm/PLIST b/security/srm/PLIST
new file mode 100644
index 00000000000..621fd2154b4
--- /dev/null
+++ b/security/srm/PLIST
@@ -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 --git a/security/srm/distinfo b/security/srm/distinfo
new file mode 100644
index 00000000000..dc0be63cb50
--- /dev/null
+++ b/security/srm/distinfo
@@ -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