From ac3c0f5e682b6fd6c95a3ca6df24b744d7165055 Mon Sep 17 00:00:00 2001 From: LEVAI Daniel Date: Sun, 5 Nov 2017 20:50:14 +0000 Subject: system/ecryptfs-utils: Added (cryptographic filesystem). Signed-off-by: David Spencer --- system/ecryptfs-utils/README | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 system/ecryptfs-utils/README (limited to 'system/ecryptfs-utils/README') diff --git a/system/ecryptfs-utils/README b/system/ecryptfs-utils/README new file mode 100644 index 0000000000000..44fbafb7c282d --- /dev/null +++ b/system/ecryptfs-utils/README @@ -0,0 +1,15 @@ +eCryptfs is a cryptographic stacked Linux filesystem. eCryptfs stores +cryptographic metadata in the header of each file written, so that encrypted +files can be copied between hosts; the file will be decrypted with the proper +key in the Linux kernel keyring. There is no need to keep track of any +additional information aside from what is already in the encrypted file +itself. You may think of eCryptfs as a sort of "gnupgfs", or "gnupg as a +filesystem". + +On Slackware, the Slackbuild script does not install the mount helper binaries +into /sbin, but to /usr/sbin. Because of this, using `mount -t ecryptfs` won't +work, and you must call the `[u]mount.ecryptfs*` binaries explicitly. + +For an unprivileged user to use the `[u]mount.ecryptfs_private` executables, +it is necessary to set the suid bit on them, which the Slackbuild script also +does not do. -- cgit v1.2.3