mirror of
https://git.freebsd.org/ports.git
synced 2025-04-28 01:26:39 -04:00
6e2da9672f
The filesystems category houses file systems and file system utilities. It is added mainly to turn the sysutils/fusefs-* pseudo-category into a proper one, but is also useful for the sundry of other file systems related ports found in the tree. Ports that seem like they belong there are moved to the new category. Two ports, sysutils/fusefs-funionfs and sysutils/fusefs-fusepak are not moved as they currently don't fetch and don't have TIMESTAMP set in their distinfo, but that is required to be able to push a rename of the port by the pre-receive hook. Approved by: portmgr (rene) Reviewed by: mat Pull Request: https://github.com/freebsd/freebsd-ports/pull/302 PR: 281988
17 lines
989 B
Text
17 lines
989 B
Text
CryptoFS is a encrypted filesystem for Filesystem in Userspace (FUSE) and
|
|
the Linux Userland FileSystem (LUFS). Visit http://fuse.sourceforge.net/
|
|
for more information on FUSE, or http://lufs.sourceforge.net/lufs/ for
|
|
more information on 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.
|
|
|
|
CryptoFS can be build for FUSE, and LUFS. When you build for FUSE you get
|
|
a program to mount the filesystem. For LUFS a shared library will be built
|
|
that can be used by LUFS's lufsd. Both methods can use the same encrypted
|
|
directory.
|