nwipe

nwipe

nwipe is a fork of the dwipe command originally used by Darik's Boot and Nuke (DBAN).
It was created to run the DBAN erase engine on any Linux distribution, with better and more modern hardware support.

• What's new?
• Erasure methods
• PRNG engines
• I/O subsystem
  • Large, aligned I/O buffers
  • I/O mode selection
  • Sync behaviour
• ATA (SSD) & NVMe Secure Erase
• Compiling & Installing
  • Dependencies
  • Debian & Ubuntu prerequisites
  • Fedora / RHEL / CentOS Stream prerequisites
  • Arch Linux / Manjaro prerequisites
  • openSUSE (Leap / Tumbleweed) prerequisites
  • NVMe Secure Erase prerequisites
  • Compilation
• Hacking
• Automating download and compilation (Debian-based distros)
• Quick & easy, USB bootable version of nwipe master for x86_64 systems
• Which Linux distro uses the latest nwipe?
• Bugs
• License

nwipe securely erases the entire contents of block devices. It can wipe a single drive or multiple disks in parallel, either:

• as a command-line tool without a GUI, or
• with an ncurses-based GUI, as shown below:

[!WARNING] For some of nwipe’s features such as SMART data in the PDF certificate, HPA/DCO detection and other functions, nwipe uses external tools: smartmontools and hdparm. Both hdparm and smartmontools are mandatory if you want all nwipe features to be fully available. If they are not installed at runtime, nwipe will log a warning and continue, but many important features will not work as intended.

The animation above shows six drives being erased in parallel. The view jumps to the completion of all six wipes and shows five drives successfully wiped and one that failed due to an I/O error. The failing drive would typically be physically destroyed. Drives that complete with zero errors can be safely redeployed.

The screenshot above shows nwipe’s three–page PDF certificate. Drive-identifying data such as serial numbers has been anonymised using the -q / --quiet option.

What's new?

Refer to our CHANGELOG document to see exactly what's changed.

Erasure methods

The user can select from a variety of recognised secure erase methods, including:

• Fill With Zeros
  Fills the device with zeros (0x00).

• Fill With Ones
  Fills the device with ones (0xFF).

• RCMP TSSIT OPS-II
  Royal Canadian Mounted Police Technical Security Standard, OPS-II.

• DoD 5220.22-M (Short)
  U.S. Department of Defense 5220.22-M short 3-pass wipe (passes 1, 2 & 7).

• DoD 5220.22-M (Full)
  U.S. Department of Defense 5220.22-M full 7-pass wipe.

• Gutmann Wipe
  Peter Gutmann's 35-pass method (“Secure Deletion of Data from Magnetic and Solid-State Memory”).

• PRNG Stream
  Fills the device with a stream generated by the selected PRNG engine.

• Verify Zeros
  Reads the device and verifies it is filled with zeros (0x00).

• Verify Ones
  Reads the device and verifies it is filled with ones (0xFF).

• HMG IS5 Enhanced
  UK HMG IS5 (Enhanced) sanitisation method for protectively marked or sensitive information.

• Schneier Wipe
  Bruce Schneier's 7-pass mixed–pattern algorithm.

• BMB21-2019 (new in v0.40)
  Chinese State Secrets Bureau BMB21-2019 technical requirement for data sanitisation.

• Standalone Secure Erase (Block, Crypto Scramble, Overwrite) (new in v0.43)
  Performs interactive, standalone, hardware-native drive sanitization—utilizing the drive's native ATA/NVMe block erase, cryptographic scramble, or pattern overwriting directly from nwipe's GUI.

PRNG engines

nwipe includes multiple pseudorandom number generators (PRNGs) for methods that require random data:

• XORoshiro-256
  Very fast, high–quality non-cryptographic generator, suitable for high–volume random wiping where a CSPRNG is not strictly required.

• Additive Lagged Fibonacci Generator Implementation of the Additive Lagged Fibonacci Generator (ALFG).

• ISAAC-64 (CSPRNG)
  Cryptographically secure, (Indirection, Shift, Accumulate, Add, and Count) generators (64 bit variant).

• ISAAC (CSPRNG)
  Cryptographically secure, (Indirection, Shift, Accumulate, Add, and Count) generators (32 bit variant).

• Mersenne Twister
  Well-known high–period PRNG.

• AES-256-CTR (CSPRNG) (new in v0.40)
  Cryptographically secure, high–throughput counter-mode stream cipher, using hardware AES-NI where available.

• SplitMix64 (new in v0.41)
  General-purpose non-cryptographic generator, optimized for 64-bit architectures.

• ChaCha20 (CSPRNG) (new in v0.41)
  Cryptographically secure, no special hardware requirements, as used worldwide in TLS and SSH.

These PRNGs can be selected at runtime (see the man page for the exact CLI options) and are used by any wipe method that requires random patterns (for example PRNG Stream, Schneier or BMB21 random passes).

I/O subsystem

Starting with v0.40 the nwipe I/O layer has been significantly modernised:

Large, aligned I/O buffers

nwipe now uses large, aligned multi-megabyte buffers when reading and writing:

• Reduces the number of read() / write() calls.
• Improves throughput on fast devices (SSD / NVMe / high-speed RAID).
• Ensures correct alignment for Direct I/O (O_DIRECT) where supported.

I/O mode selection

You can now explicitly control how nwipe accesses the device:

--io-mode=auto      # default
--io-mode=direct    # equivalent to --directio
--io-mode=cached    # equivalent to --cachedio

--directio          # force O_DIRECT (no fallback)
--cachedio          # force kernel cached I/O only

• auto Try to open the device with O_DIRECT. If the kernel or filesystem does not support it (EINVAL/EOPNOTSUPP), nwipe falls back to cached I/O and logs a warning.

• direct / --directio Force Direct I/O. If O_DIRECT is not supported for the device, opening the device fails and the wipe will not proceed. This is useful for strict testing and benchmarking.

• cached / --cachedio Always use kernel buffered I/O. O_DIRECT is never attempted. This is closest to the behaviour of older nwipe releases.

Sync behaviour

The --sync option controls how often nwipe performs fdatasync() when using cached I/O:

• The value represents the number of device hardware blocks (typically 512 or 4096 bytes) between syncs.

• Internally this value is scaled to match nwipe’s large I/O buffer size so that the effective bytes between syncs remain in a reasonable range (tens to hundreds of MB, depending on the default and device).

• This ensures:

  • timely detection of I/O and hardware errors in cached I/O mode, and
  • good throughput for normal use.

In Direct I/O mode (--directio / --io-mode=direct), periodic sync is disabled: write errors are reported immediately by write(), so fdatasync() provides no additional safety.

See the nwipe(8) man page for detailed --sync semantics and examples.

ATA (SSD) & NVMe Secure Erase

The v0.43 release introduces several major improvements.

Nwipe is now able to sanitize ATA and NVMe devices using native hardware capabilities.

A regular wipe was often not enough for flash storage devices:

• SSDs use wear-levelling and additional, non-host-accessible memory (overprovisioning).
• Failed blocks may be remapped to reserved areas that are not directly addressable by the OS.
• Many vendors restrict low-level access to these areas to the drive’s own controller and firmware.

For secure flash storage sanitization, the firmware can implement native secure erase methods.

These hardware methods ensure that even such non-accessible parts of a device are safely erased.

Nwipe is now able to detect these and will offer to utilize secure erase methods from within the GUI:

It is strongly recommended to sanitize devices using the available secure erase methods, and then always follow up with at least one full regular PRNG wipe afterwards (both are possible in the GUI).

If no secure erase methods are offered for your device, try connecting it directly to the motherboard. This is especially true for ATA devices (watch out for bad sense data errors in the logs), which benefit greatly from not having to talk to Nwipe through cheap or generic USB/SATA/RAID controllers.

For devices that cannot be detected or as an alternative, the previous guidance is still valid:

1. Use nwipe / ShredOS in combination with vendor-specific tools, for example:

   • manufacturer Secure Erase,
   • NVMe format / sanitize commands, or
   • hardware vendor–provided utilities, and

2. Independently validate the result, comparing drive contents before and after sanitisation where feasible.

A list of common SSD vendor tools and guidance can be found in the separate SSD Guide.

Compiling & Installing

For development work, see the Hacking section below. For a bootable image with the latest nwipe master that you can write to a USB stick or CD/DVD, see Quick & easy, USB bootable version.

Dependencies

nwipe requires at compile-time the following libraries:

• ncurses
• pthreads
• parted
• libconfig
• libnvme

nwipe requires at runtime and will abort with a warning if not found:

• hdparm (as of current master and v0.35+)

The following auxiliary tools are optional but strongly recommended:

• dmidecode
• coreutils (for readlink)
• smartmontools

These tools enable features such as:

• HPA/DCO detection
• SMART data for PDF certificates (especially for USB bridge devices)
• SMBIOS/DMI host information in the log
• Correct bus type detection (ATA/USB/etc.) and proper operation of --nousb

Debian & Ubuntu prerequisites

If you are compiling nwipe from source on Debian & Ubuntu:

sudo apt install \
  build-essential \
  pkg-config \
  automake \
  libncurses5-dev \
  autotools-dev \
  libparted-dev \
  libconfig-dev \
  libconfig++-dev \
  dmidecode \
  coreutils \
  smartmontools \
  hdparm \
  libnvme-dev

Fedora / RHEL / CentOS Stream prerequisites

If you are compiling nwipe from source on Fedora / RHEL / CentOS:

sudo bash
sudo dnf update -y
sudo dnf groupinstall -y "Development Tools" "C Development Tools and Libraries"
sudo dnf install -y \
  ncurses-devel \
  parted-devel \
  libconfig-devel \
  libconfig++-devel \
  dmidecode \
  coreutils \
  smartmontools \
  hdparm \
  libnvme-devel

Arch Linux / Manjaro prerequisites

If you are compiling nwipe from source on Arch Linux / Manjaro:

sudo pacman -Syu --needed \
  base-devel \
  ncurses \
  parted \
  libconfig \
  dmidecode \
  coreutils \
  smartmontools \
  hdparm \
  libnvme

openSUSE (Leap / Tumbleweed) prerequisites

If you are compiling nwipe from source on openSUSE:

sudo zypper refresh
sudo zypper install -y \
  gcc \
  make \
  automake \
  autoconf \
  libtool \
  ncurses-devel \
  libparted-devel \
  libconfig-devel \
  libconfig++-devel \
  dmidecode \
  coreutils \
  smartmontools \
  hdparm \
  libnvme-devel

NVMe Secure Erase prerequisites

[!WARNING] Nwipe was specifically tested aga