Secure wipe

From Gentoo Wiki
Jump to:navigation Jump to:search

Once data has been stored on a disk, it may not be straightforward to remove that data, being sure that it cannot be read again. Securely wiping memory can differ depending on the memory type, as well as how it is interfaced with. The main obstacle in securely erasing a drive is Data Remanence, or residual data remaining on the drive.


Erasing portions of storage is often unnecessary, this is because it is simpler faster to just unlink data instead of wiping it. Wiping data requires the region of memory to be totally overwritten, and this can be a very slow process.


Planning in advance, and never writing plaintext data on a drive can help in preventing data recovery, especially recovery using inaccessible data regions. If only encrypted data has been written to a disk, through the use of Full Disk Encryption, or other methods, deleting the key is typically enough to prevent data recovery.

This is literally like locking something and throwing away the key.

Wiping Woes

Or, why wiping storage is not always simple.

Advanced Data Recovery

Even if an entire drive is overwritten with 0s, that does not guarantee that data cannot be recovered, especially if transparent compression is being used. Doing multiple overwrite passes with random data is typically required to be reasonably certain that data cannot be recovered. Wiping using random data is typically slower, and also requires good entropy sources for any amount of speed.

A single pass with random data is typically enough to stop recovery, especially on modern, high-capacity drives, but doesn't affect inaccessible memory regions.

Inaccessible Memory Regions

Modern hard drives often come with more available storage than the controller allows usage of. This allows the drive to reallocate data when it detects that memory is degrading. This over-provision is especially relevant to SSDs, which can physically only write each section of memory a limited amount of times before it fails. Depending on the drive, software methods used to overwrite all memory may have no way to touch this now deallocated memory.

Write Only Memory

Data written to any form of write-only memory, such as CD-Rs cannot be overwritten or erased, so the storage must be destroyed to prevent data recovery.


USE Flags

USE flags for sys-apps/hdparm Utility to change hard drive performance parameters

static !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically

USE flags for sys-apps/nvme-cli NVM-Express user space tooling for Linux

hugepages Use huge pages for memory allocations via sys-libs/libhugetlbfs
json Support JSON output via dev-libs/json-c


root #emerge --ask sys-apps/hdparm
root #emerge --ask sys-apps/nvme-cli

Methods of Destruction


If data recovery is ever a concern for a storage device, encryption should be the first line of defense. In the event the device is obtained before it could be wiped, the data should already be useless, unless the keys were stored with the device, making decryption easy.

If a device is encrypted using LUKS, wiping the headers is enough to render the data useless, so long as backups do not exist.

If /dev/sda1 is LUKS encrypted, all keys can be removed from the header with:

root #cryptsetup erase /dev/sda1
LUKS keys can be checked using
root #cryptsetup luksDump /dev/sda1

With no keys installed, there is no way the partition can be decrypted. To totally remove the LUKS header:

root #wipefs --all /dev/sda
This process doesn't actually remove any of the data that was written to the drive, it simply removes the metadata used for accessing it, making it irrecoverable with modern technology.


Generic Methods

shred is part of GNU coreutils and should be preinstalled on most Gentoo based systems.

shred can only overwrite regions which the storage controller allows writing to, potentially leaving some recoverable data. Wear leveling on SSD's can also result in data being left behind until that cell is reused.

shred can be used to erase /dev/sda using one pass of pseudorandom data sourced from /dev/urandom:

root #shred --verbose --random-source /dev/urandom --iterations 1 /dev/sda


hdparm can be used to execute an ATA Secure Erase command. A Secure Erase command should handle wiping inaccessible regions.

In order to execute a SATA Secure Erase, a password must be set for the device, this password will be removed during the erase process:

root #hdparm --security-set-pass NULL /dev/sda
security_password: ""

 Issuing SECURITY_SET_PASS command, password="", user=user, mode=high

With the password set, the drive can be erased using:

root #hdparm --security-erase NULL /dev/sda
security_password: ""

 Issuing SECURITY_ERASE command, password="", user=user
An ATA secure erase command should be executed over a proper SATA interface, not a USB interface, this is because the command is executed by the firmware, taking the drive offline while it executes. The USB controller may try to "help" by resetting the device, interrupting the erase.[1]


A firmware secure erase can be executed on a NVME drive using:

root #nvme format --ses 1 /dev/nvmeXnY