|
|
|
|
|
by masklinn
3690 days ago
|
|
> This functionality already exists in GNU coreutils, it's done by the shred(1) command. No need to install any extra third-party software, shred is already installed. That's only true for GNU-based userlands, not BSD-based ones. > Also, as another commenter already pointed out, this kind of in-place overwrite is not guaranteed to work on SSDs And if the system properly TRIMs it might not be necessary at all, though that greatly depends on the SSD. |
|
Sure, but installing (a subset of) GNU coreutils is probably going to pull in a lot fewer dependencies than this JavaScript command line tool. Plus, you can use ports, no need to mess with a seperate package manager (npm) and the associated package verification foibles.
> And if the system properly TRIMs it might not be necessary at all, though that greatly depends on the SSD.
The "depends on the SSD" is a big one. Various recent forensic papers have shown that it can take a while until a TRIM'd sector is actually erased by the firmware.
I still think that if this kind of thing causes worries, full-disk encryption is really the only sensible solution.