summaryrefslogtreecommitdiff
path: root/system/cryptofs/README
diff options
context:
space:
mode:
authorPierre Cazenave <pwcazenave@gmail.com>2010-05-11 20:01:56 +0200
committerRobby Workman <rworkman@slackbuilds.org>2010-05-11 20:01:56 +0200
commitc0c52031fb9b0593d7f326a71ef7c235865137e8 (patch)
treecb9c8deb225f410f584468dcef04aa06e2df679f /system/cryptofs/README
parent898b3ce8c9b4dedc1830ab83cf139d619ab8fcc7 (diff)
downloadslackbuilds-c0c52031fb9b0593d7f326a71ef7c235865137e8.tar.gz
system/cryptofs: Added to 12.0 repository
Diffstat (limited to 'system/cryptofs/README')
-rw-r--r--system/cryptofs/README14
1 files changed, 14 insertions, 0 deletions
diff --git a/system/cryptofs/README b/system/cryptofs/README
new file mode 100644
index 0000000000..ff31de135d
--- /dev/null
+++ b/system/cryptofs/README
@@ -0,0 +1,14 @@
+CryptoFS is a encrypted filesystem for Filesystem in Userspace (FUSE)
+and the Linux Userland FileSystem (LUFS).
+
+CryptoFS will use a normal directory to store files encrypted. The
+mountpoint will contain the decrypted files. Every file stored in
+this mountpoint will be written encrypted (data and filename) to the
+directory that was mounted. If you unmount the directory the encrypted
+data can only be access by mounting the directory with the correct key
+again. Like other FUSE/LUFS filesystems it does not need root access
+or any complicated setup like creating a filesystem on a encrypted disk
+using the loop device.
+
+This requires fuse (also available at SlackBuilds.org), although it can
+alternatively use LUFS if you have that installed from elsewhere.