diff options
| author |   B. Watson | 2022-03-14 17:53:16 +0100 |
|---|---|---|
| committer | B. Watson | 2022-03-17 17:38:12 +0100 |
| commit | cb375e0a102b321b8b90469a22388bc22196ce63 (patch) | |
| tree | c2ec68f6114e93735fe10e69f8b57683dac4b1c4 /system/srm | |
| parent | 97cb813d03cf701b0418aa6e0a4e226362464bd3 (diff) | |
| download | slackbuilds-cb375e0a102b321b8b90469a22388bc22196ce63.tar.gz | |
system/srm: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/srm')
| -rw-r--r-- | system/srm/README | 28 |
1 files changed, 15 insertions, 13 deletions
diff --git a/system/srm/README b/system/srm/README index a2c86552ed..906440e880 100644 --- a/system/srm/README +++ b/system/srm/README @@ -1,15 +1,17 @@ -srm is a secure replacement for rm(1). Unlike the standard rm, it overwrites -the data in the target files before unlinking them. This prevents command-line -recovery of the data by examining the raw block device. It may also help to -frustrate a physical examination of the disk, although it's unlikely that it can -completely protect against this type of recovery. +srm is a secure replacement for rm(1). Unlike the standard rm, it +overwrites the data in the target files before unlinking them. This +prevents command-line recovery of the data by examining the raw block +device. It may also help to frustrate a physical examination of the +disk, although it's unlikely that it can completely protect against +this type of recovery. -srm uses algorithms found in "Secure Deletion of Data from Magnetic and Solid- -State Memory" by Peter Gutmann and THC Secure Delete (the overwrite, truncate, -rename, unlink sequence). +srm uses algorithms found in "Secure Deletion of Data from Magnetic +and Solid- State Memory" by Peter Gutmann and THC Secure Delete (the +overwrite, truncate, rename, unlink sequence). -Please note that srm will only work on file systems that overwrite blocks in -place. In particular, it will *NOT* work on reiserfs or the vast majority of -journaled file systems. It should work on ext2, FAT-based file systems, and -the BSD native file system. On ext3, srm will try to disable the journaling -of data (please see the verbose output if this fails). +Please note that srm will only work on file systems that overwrite +blocks in place. In particular, it will *NOT* work on reiserfs or +the vast majority of journaled file systems. It should work on ext2, +FAT-based file systems, and the BSD native file system. On ext3, srm +will try to disable the journaling of data (please see the verbose +output if this fails). |