2011-01-10 07:13:37 +01:00
|
|
|
# $NetBSD: Makefile,v 1.5 2011/01/10 06:13:37 obache Exp $
|
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.
2004-08-16 22:15:54 +02:00
|
|
|
#
|
|
|
|
|
|
|
|
|
|
DISTNAME= wipe-2.2.0
|
|
|
|
|
CATEGORIES= sysutils
|
|
|
|
|
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=wipe/}
|
|
|
|
|
EXTRACT_SUFX= .tar.bz2
|
|
|
|
|
|
2010-07-06 12:17:11 +02:00
|
|
|
MAINTAINER= pkgsrc-users@NetBSD.org
|
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.
2004-08-16 22:15:54 +02:00
|
|
|
HOMEPAGE= http://wipe.sourceforge.net/
|
|
|
|
|
COMMENT= Secure data destruction
|
2011-01-10 07:13:37 +01:00
|
|
|
LICENSE= gnu-gpl-v2
|
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.
2004-08-16 22:15:54 +02:00
|
|
|
|
|
|
|
|
PKG_INSTALLATION_TYPES= overwrite pkgviews
|
2010-01-27 21:28:15 +01:00
|
|
|
PKG_DESTDIR_SUPPORT= user-destdir
|
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.
2004-08-16 22:15:54 +02:00
|
|
|
|
|
|
|
|
GNU_CONFIGURE= yes
|
|
|
|
|
|
|
|
|
|
.include "../../mk/bsd.pkg.mk"
|
