summaryrefslogtreecommitdiff
path: root/system/srm/README
diff options
context:
space:
mode:
authorMarco Bonetti <sid77@slackware.it>2010-05-13 01:01:10 +0200
committerDavid Somero <xgizzmo@slackbuilds.org>2010-05-13 01:01:10 +0200
commit6684de1a477a46179cc66772d9ebe20540d31165 (patch)
tree402393cf9a23c0c2bf242341be6287994fa37ca2 /system/srm/README
parent4d4710b1beb39c8171f4d8ca0fbb7981ddce3263 (diff)
downloadslackbuilds-6684de1a477a46179cc66772d9ebe20540d31165.tar.gz
system/srm: Added to 13.0 repository
Diffstat (limited to 'system/srm/README')
-rw-r--r--system/srm/README14
1 files changed, 14 insertions, 0 deletions
diff --git a/system/srm/README b/system/srm/README
new file mode 100644
index 0000000000..d231d5aafa
--- /dev/null
+++ b/system/srm/README
@@ -0,0 +1,14 @@
+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
+frustrate physical examination of the disk, although it's unlikely that it can
+completely prevent that type of recovery. It is, essentially, a paper shredder
+for sensitive files.
+
+srm is ideal for personal computers or workstations with Internet connections.
+It can help prevent malicious users from breaking in and undeleting personal
+files, such as old emails. It's also useful for permanently removing files
+from expensive media. For example, cleaning your diary off the zip disk you're
+using to send vacation pictures to Uncle Lou. Because it uses the exact same
+options as rm(1), srm is simple to use. Just subsitute it for rm whenever you
+want to destroy files, rather than just unlinking them.