kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/sysutils/wipe/distinfo

14 lines
823 B
Text
Raw Normal View History

sysutils: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes
2021-10-26 13:19:17 +02:00
$NetBSD: distinfo,v 1.11 2021/10/26 11:20:23 nia 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
sysutils: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes
2021-10-26 13:19:17 +02:00
BLAKE2s (wipe-2.3.1.tar.bz2) = d2a063369731c7ce5943651b433ff72b1b0446631fdacb523278f638d2895be0
(sysutils/wip) Updated 2.2.0 to 2.3.1 2.3.1: fixed Makefile bug! Running make uninstall removed target bin directory. 2.3: DEFAULTS! the default is now one single random pass <-- MAJOR CHANGE special files are no longer deleted by default support for wiping char devices, such as tape drives percentage reporting improved (thanks to Jason Tackaberry for patch) cleanup and exit upon SIGINT each wiped file prints on a seperate line skip unnecessary fdatasync()s, unless you want the extra accuracy on the % shown (-e option) call fsync() on the file after name wipe, in addition to fsync on the directory if fdatasync() fails, try for O_SYNC and only complain once per file fixed some off-by-ones fixed percentages for non-static wipes 2.2.1: added largefile support for linux and solaris (tested on linux) fixed drill_down(). it was using the wrong length to null term the string
2019-11-16 11:14:15 +01:00
SHA512 (wipe-2.3.1.tar.bz2) = 63870e68fa5dbf90abb686052f8dcc216ccb93b0c4f5cc10d60ccf43f3606ba91b46dc1e3d8b34d201f7ea657f70b45a61d5d04facf5b2a3e47d2286c46e7110
Size (wipe-2.3.1.tar.bz2) = 72297 bytes
SHA1 (patch-aa) = d4045fb2cfb620f0cbf7f5b767b42805389875a5
SHA1 (patch-ab) = c870f718cbba7e633dd2a2e6e6da20d2dd942c26
SHA1 (patch-ac) = 742517caf37193a254245685d5d7cd990caab7a5
SHA1 (patch-ad) = 8867747f6e91d28e507de3b24c9436e3756d3652
SHA1 (patch-ae) = 9785777c93b3c2fb357fcca4ba73f2f5bf5a8329
SHA1 (patch-af) = 98c17d8fcb00b2e4327294dd26b367b874eacfe2
SHA1 (patch-ag) = 1c2944e07724c27abbd4c966822159e649ac786a
Use DIOCGINFO and/or DIOCGWEDGEINFO if DIOCGPART isn't defined. Fixes build on netbsd-6 and up. Caution: while it builds, I haven't actually tested it.
2013-06-17 08:09:06 +02:00
SHA1 (patch-ah) = 362b9f59453baa4d8632d895a2f3a530ba9ca652
Reference in a new issue Copy permalink