diff options
author | minskim <minskim@pkgsrc.org> | 2004-08-16 20:15:54 +0000 |
---|---|---|
committer | minskim <minskim@pkgsrc.org> | 2004-08-16 20:15:54 +0000 |
commit | 50f16151799e192c9da32fdfb9ffba671f0a86fe (patch) | |
tree | ce78a8fd5662e68898104ee5e367af9592eda55e /sysutils/wipe | |
parent | f8e539f4d692a22d534bb2b44adfaef10badd989 (diff) | |
download | pkgsrc-50f16151799e192c9da32fdfb9ffba671f0a86fe.tar.gz |
Import wipe from pkgsrc-wip. Packaged by pancake and modified by me.
Wipe is a secure file wiping utility.
There are some low level issues that must be taken into consideration.
One of these is that there must be some sort of write barrier between
passes. Wipe uses fdatasync(2) (or fsync(2)) as a write barrier, or
if fsync(2) isn't available, the file is opened with the O_DSYNC or
O_SYNC flag. For wipe to be effective, each pass must be completely
written. To ensure this, the drive must support some form of a write
barrier, write cache flush, or write cache disabling. SCSI supports
ordered command tags, has a force media access bit for commands, and
write cache can be disable on mode page 8. IDE/ATA drives support
write cache flushes and write cache disabling.
Unfortunately, not all drives actually disable write cache when asked
to. Those drives are broken. Write caching should always be
disabled, unless your system is battery backed and always powers down
cleanly.
Diffstat (limited to 'sysutils/wipe')
-rw-r--r-- | sysutils/wipe/DESCR | 17 | ||||
-rw-r--r-- | sysutils/wipe/Makefile | 18 | ||||
-rw-r--r-- | sysutils/wipe/PLIST | 11 | ||||
-rw-r--r-- | sysutils/wipe/distinfo | 5 | ||||
-rw-r--r-- | sysutils/wipe/patches/patch-aa | 26 |
5 files changed, 77 insertions, 0 deletions
diff --git a/sysutils/wipe/DESCR b/sysutils/wipe/DESCR new file mode 100644 index 00000000000..a20578a5a03 --- /dev/null +++ b/sysutils/wipe/DESCR @@ -0,0 +1,17 @@ +Wipe is a secure file wiping utility. + +There are some low level issues that must be taken into consideration. +One of these is that there must be some sort of write barrier between +passes. Wipe uses fdatasync(2) (or fsync(2)) as a write barrier, or +if fsync(2) isn't available, the file is opened with the O_DSYNC or +O_SYNC flag. For wipe to be effective, each pass must be completely +written. To ensure this, the drive must support some form of a write +barrier, write cache flush, or write cache disabling. SCSI supports +ordered command tags, has a force media access bit for commands, and +write cache can be disable on mode page 8. IDE/ATA drives support +write cache flushes and write cache disabling. + +Unfortunately, not all drives actually disable write cache when asked +to. Those drives are broken. Write caching should always be +disabled, unless your system is battery backed and always powers down +cleanly. diff --git a/sysutils/wipe/Makefile b/sysutils/wipe/Makefile new file mode 100644 index 00000000000..a34d0eb8276 --- /dev/null +++ b/sysutils/wipe/Makefile @@ -0,0 +1,18 @@ +# $NetBSD: Makefile,v 1.1.1.1 2004/08/16 20:15:54 minskim Exp $ +# + +DISTNAME= wipe-2.2.0 +CATEGORIES= sysutils +MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=wipe/} +EXTRACT_SUFX= .tar.bz2 + +MAINTAINER= pancake@phreaker.net +HOMEPAGE= http://wipe.sourceforge.net/ +COMMENT= Secure data destruction + +PKG_INSTALLATION_TYPES= overwrite pkgviews + +USE_BUILDLINK3= yes +GNU_CONFIGURE= yes + +.include "../../mk/bsd.pkg.mk" diff --git a/sysutils/wipe/PLIST b/sysutils/wipe/PLIST new file mode 100644 index 00000000000..37c522abe77 --- /dev/null +++ b/sysutils/wipe/PLIST @@ -0,0 +1,11 @@ +@comment $NetBSD: PLIST,v 1.1.1.1 2004/08/16 20:15:54 minskim Exp $ +bin/wipe +man/man1/wipe.1 +share/doc/wipe/CHANGES +share/doc/wipe/INSTALL +share/doc/wipe/LICENSE +share/doc/wipe/README +share/doc/wipe/TESTING +share/doc/wipe/TODO +share/doc/wipe/copyright +@dirrm share/doc/wipe diff --git a/sysutils/wipe/distinfo b/sysutils/wipe/distinfo new file mode 100644 index 00000000000..26b8bfc65fb --- /dev/null +++ b/sysutils/wipe/distinfo @@ -0,0 +1,5 @@ +$NetBSD: distinfo,v 1.1.1.1 2004/08/16 20:15:54 minskim Exp $ + +SHA1 (wipe-2.2.0.tar.bz2) = 4dd18f260ecd91b726336b2788fa33db04d6691a +Size (wipe-2.2.0.tar.bz2) = 70134 bytes +SHA1 (patch-aa) = d40a3324eb5e8473d7a3a6acbc307c2ab63d60de diff --git a/sysutils/wipe/patches/patch-aa b/sysutils/wipe/patches/patch-aa new file mode 100644 index 00000000000..207e315793e --- /dev/null +++ b/sysutils/wipe/patches/patch-aa @@ -0,0 +1,26 @@ +$NetBSD: patch-aa,v 1.1.1.1 2004/08/16 20:15:54 minskim Exp $ + +--- Makefile.in.orig 2003-08-30 20:18:03.000000000 -0500 ++++ Makefile.in +@@ -57,15 +57,15 @@ info: $(BIN_OUT) + @ldd $(BIN_OUT) + + install: $(BIN_OUT) +- $(INSTALL_BIN) -d $(bindir) +- $(INSTALL_BIN) -s $(BIN_OUT) $(bindir) +- $(INSTALL) -d $(mandir)/man1 +- $(INSTALL) -o root -m 0644 wipe.1 $(mandir)/man1/ ++ $(BSD_INSTALL_PROGRAM_DIR) $(bindir) ++ $(BSD_INSTALL_PROGRAM) $(BIN_OUT) $(bindir) ++ $(BSD_INSTALL_MAN_DIR) $(mandir)/man1 ++ $(BSD_INSTALL_MAN) wipe.1 $(mandir)/man1/ + rm -rf $(datadir)/doc/wipe* +- $(INSTALL) -d $(datadir)/doc/wipe ++ $(BSD_INSTALL_DATA_DIR) $(datadir)/doc/wipe + + for file in $(DOCS); do \ +- $(INSTALL) -o root -m 0644 $$file $(datadir)/doc/wipe/; \ ++ $(BSD_INSTALL_DATA) $$file $(datadir)/doc/wipe/; \ + done + + install_home: $(BIN_OUT) |