From d7d60467b4cb23012e5b56dbeddc2ad08050db5c Mon Sep 17 00:00:00 2001 From: Alex Anderson Date: Tue, 28 Jun 2022 07:28:00 +0000 Subject: [PATCH] Fixed minor mistake --- guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide.md b/guide.md index 8acb3a7..b128fd8 100644 --- a/guide.md +++ b/guide.md @@ -8231,7 +8231,7 @@ So, you want to be sure. To achieve 100% secure deletion on an SSD drive, we wil - If using `srm`, make sure to manually specify that it should perform a Gutmann wipe (`srm -G /dev/sdX`). - SSDs: - Overwrite the drive's contents. Tools like wipe or shred are often overkill, as they perform up to 35 passes. While they work, most SSDs require no more than a couple passes. - - Use `wipe` with only a couple passes: `wipe -qQ2 /dev/sdX` (`-qQ2` means to passes. Replace `2` with the desired number of passes) + - Use `wipe` with only a couple passes: `wipe -qQ2 /dev/sdX` (`-qQ2` means 2 passes. Replace `2` with the desired number of passes) - Use `srm` with a 3-pass overwrite: `srm -P /dev/sdX` - Use `dd`: `dd if=/dev/urandom of=/dev/sdX bs=8M status=progress conv=fsync`. This command will overwrite the drive with random data. To perform multiple passes (I recommend at least 2), simply run the command again until you're satisfied. - The reason you run it twice is because SSDs have hidden ("overprovisioned") storage which can contain remnants of deleted data. Wiping twice forces the drive to wipe its overprovisioned storage. This is only guaranteed to work if each pass writes different data (which is why we wipe with random data on each pass).