Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
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.
