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.
This commit is contained in:
parent
658f3a6c64
commit
24dcecdd5f
4 changed files with 38 additions and 0 deletions
16
security/srm/DESCR
Normal file
16
security/srm/DESCR
Normal file
|
@ -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.
|
15
security/srm/Makefile
Normal file
15
security/srm/Makefile
Normal file
|
@ -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"
|
3
security/srm/PLIST
Normal file
3
security/srm/PLIST
Normal file
|
@ -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
|
4
security/srm/distinfo
Normal file
4
security/srm/distinfo
Normal file
|
@ -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
|
Loading…
Reference in a new issue