notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Remember
I remember
2024-11-06 Today brought in a new category: filesystems. Sadly, the website did not process it well. I am working on that. It may take a few days.
2024-11-07 Commit processing is halted. I have a fix for the new category. It is making its way through the system.
UPDATE: the backend is processing the original filesystems commit now. It should take about an hour.
UPDATE: as of 20:30 UTC, the filesystems commit has been processed. Commit processing is now up to date.
Port details
cryptofs Encrypted filesystem for FUSE
0.6.0_7 filesystemsnew! on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one.
Maintainer: portmaster@BSDforge.com search for ports maintained by this maintainer
Port Added: 2024-11-07 19:52:55
Last Update: 2024-11-06 15:17:35
Commit Hash: 6e2da96
License: GPLv2+
WWW:
https://BSDforge.com/projects/sysutils/fusefs-cryptofs/
Description:
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.
Homepage    cgit ¦ Codeberg ¦ GitHub ¦ GitLab ¦ SVNWeb - no subversion history for this port

Manual pages:
FreshPorts has no man page information for this port.
pkg-plist: as obtained via: make generate-plist
Expand this list (9 items)
Collapse this list.
  1. /usr/local/share/licenses/fusefs-cryptofs-0.6.0_7/catalog.mk
  2. /usr/local/share/licenses/fusefs-cryptofs-0.6.0_7/LICENSE
  3. /usr/local/share/licenses/fusefs-cryptofs-0.6.0_7/GPLv2+
  4. bin/cryptofs
  5. share/doc/cryptofs/README
  6. share/doc/cryptofs/cryptofs.conf
  7. @owner
  8. @group
  9. @mode
Collapse this list.
Dependency lines:
  • fusefs-cryptofs>0:filesystems/cryptofs
To install the port:
cd /usr/ports/filesystems/cryptofs/ && make install clean
To add the package, run one of these commands:
  • pkg install filesystems/cryptofs
  • pkg install fusefs-cryptofs
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
PKGNAME: fusefs-cryptofs
Flavors: there is no flavor information for this port.
distinfo:
TIMESTAMP = 1730905170 SHA256 (cryptofs-0.6.0.tar.gz) = d884199e38ee09848841dda247db1db0361236b1ce8cc7dd3acb5031f80f6b57 SIZE (cryptofs-0.6.0.tar.gz) = 352805

Packages (timestamps in pop-ups are UTC):
fusefs-cryptofs
ABIaarch64amd64armv6armv7i386powerpcpowerpc64powerpc64le
FreeBSD:13:latest--------
FreeBSD:13:quarterly--------
FreeBSD:14:latest--------
FreeBSD:14:quarterly--------
FreeBSD:15:latest-0.6.0_7n/a-n/a---
Dependencies
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. pkgconf>=1.3.0_1 : devel/pkgconf
Library dependencies:
  1. libgcrypt.so : security/libgcrypt
  2. libfuse.so : filesystems/fusefs-libs
  3. libglib-2.0.so : devel/glib20
  4. libintl.so : devel/gettext-runtime
There are no ports dependent upon this port

Configuration Options:
===> The following configuration options are available for fusefs-cryptofs-0.6.0_7: DOCS=on: Build and/or install documentation ===> Use 'make config' to modify these settings
Options name:
filesystems_cryptofs
USES:
fuse gnome pkgconfig
FreshPorts was unable to extract/find any pkg message
Master Sites:
Expand this list (1 items)
Collapse this list.
  1. https://BSDforge.com/projects/source/sysutils/fusefs-cryptofs/
Collapse this list.
Port Moves

Number of commits found: 1

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
0.6.0_7
06 Nov 2024 15:17:35
commit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9dcommit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9dcommit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9dcommit hash: 6e2da9672f79f44048d597f0f61e4646cdeade9d files touched by this commit
Robert Clausecker (fuz) search for other commits by this committer
filesystems: add new category for file systems and related utilities

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

Number of commits found: 1