filesystems/securefs: Remove port

Niche use case, not aligned with broad server application needs
This commit is contained in:
2025-04-27 20:05:41 +02:00
parent 892bdae802
commit 57cf433c08
5 changed files with 1 additions and 48 deletions
+1
View File
@@ -1794,6 +1794,7 @@ filesystems/dsbmc
filesystems/kio-fuse
filesystems/openzfs
filesystems/pear-Horde_Vfs
filesystems/securefs
finance/alkimia
finance/electrum
finance/expense
-1
View File
@@ -101,7 +101,6 @@
SUBDIR += s3fs
SUBDIR += sandboxfs
SUBDIR += scan_ffs
SUBDIR += securefs
SUBDIR += simple-mtpfs
SUBDIR += smbnetfs
SUBDIR += squashfs-tools
-37
View File
@@ -1,37 +0,0 @@
PORTNAME= securefs
DISTVERSION= 1.0.0
PORTREVISION= 2
DISTVERSIONPREFIX= v
CATEGORIES= filesystems
PKGNAMEPREFIX= fusefs-
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Filesystem in userspace with transparent encryption and decryption
WWW= https://github.com/netheril96/securefs
LICENSE= MIT
LICENSE_FILE= ${WRKSRC}/LICENSE.md
BUILD_DEPENDS= ${LOCALBASE}/include/tclap/TCLAPConfig.h:devel/tclap
LIB_DEPENDS= libabsl_strings.so:devel/abseil \
libargon2.so:security/libargon2 \
libcryptopp.so:security/cryptopp \
libfruit.so:devel/fruit \
libprotobuf.so:devel/protobuf \
libuni-algo.so:textproc/uni-algo
USES= cmake compiler:c++17-lang fuse pkgconfig sqlite
CMAKE_OFF= SECUREFS_ADDRESS_SANITIZE \
SECUREFS_ENABLE_INTEGRATION_TEST \
SECUREFS_ENABLE_UNIT_TEST \
SECUREFS_LINK_PROFILER \
SECUREFS_USE_FUSET \
SECUREFS_USE_VCPKG
PLIST_FILES= bin/securefs
USE_GITHUB= yes
GH_ACCOUNT= netheril96
.include <bsd.port.mk>
-3
View File
@@ -1,3 +0,0 @@
TIMESTAMP = 1738088836
SHA256 (netheril96-securefs-v1.0.0_GH0.tar.gz) = de888359734a05ca0db56d006b4c9774f18fd9e6f9253466a86739b5f6ac3753
SIZE (netheril96-securefs-v1.0.0_GH0.tar.gz) = 417928
-7
View File
@@ -1,7 +0,0 @@
securefs is a filesystem in userspace (FUSE) with transparent encryption (when
writing) and decryption (when reading).
securefs mounts a regular directory onto a mount point. The mount point appears
as a regular filesystem, where one can read/write/create files, directories and
symbolic links. The underlying directory will be automatically updated to
contain the encrypted and authenticated contents.