Automic VaultAutomic Vault

brew

cryfs mit Homebrew, apt, dnf, MacPorts, Nix, pacman, zypper installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cryfs in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cryfs

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install cryfs

MacPorts ports tree · fuse/cryfs/Portfile · Quelle: api.github.com

Linux

Debian aptverifiziert · 92%
sudo apt install cryfs

Debian stable package indexes · cryfs · Quelle: deb.debian.org

Fedora dnfverifiziert · 92%
sudo dnf install cryfs

Fedora Rawhide package metadata · cryfs · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%
nix profile install nixpkgs#cryfs

nixpkgs package indexes · pkgs/by-name/cr/cryfs/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%
sudo pacman -S cryfs

Arch Linux sync databases · cryfs · Quelle: geo.mirror.pkgbuild.com

openSUSE zypperverifiziert · 92%
sudo zypper install cryfs

openSUSE Tumbleweed package metadata · cryfs · Quelle: download.opensuse.org

Überblick

Paketzusammenfassung

Encrypts your files so you can safely store them in Dropbox, iCloud, etc.

Befehle und Aliase

  • cryfs
  • cryfs-unmount

Verlauf

Projektgeschichte und Nutzung

CryFS is an encrypted filesystem aimed at storing data safely on cloud-sync services. In package-manager terms it sits at the intersection of FUSE filesystem tooling, local encryption utilities, and privacy-oriented desktop workflows.

Projektgeschichte

CryFS was published as an open-source cryptographic filesystem for the cloud, with its official site describing a design that encrypts content, filenames, directory structure, timestamps, and other metadata into fixed-size encrypted blocks. The official technical page cites a 2015 master's thesis and a 2017 DBSec publication for the security analysis behind the design.

Adoptionsgeschichte

The upstream README documents distribution through apt, pacman, Homebrew, MacPorts, Nix, and experimental Windows builds, and also mentions GUI integrations such as SiriKali and KDE Plasma Vault. That breadth explains why package managers carry CryFS even though it is a specialized filesystem tool: users need it installed close to the operating system, FUSE layer, and desktop integration points.

Wie es verwendet wird

A typical CryFS workflow creates a vault directory, stores an encrypted configuration file named cryfs.config there, and mounts decrypted contents through the cryfs command. Its cloud-storage focus is visible in the official examples naming Dropbox, iCloud, OneDrive, and similar services, while the docs warn about non-concurrent use and corruption risks if multiple devices or sync clients write at the same time.

Warum Paket-Nerds sich dafür interessieren

CryFS matters to packagers because it pulls ordinary package management into filesystem integration: macOS users need macFUSE, Linux users need FUSE support, Windows builds use DokanY, and the project has historically cared about distro packages as first-class install routes. The package is therefore more than a binary drop; it is a small filesystem stack with platform-specific runtime expectations.

Zeitleiste

  • 2015: The official security-analysis page cites the CryFS master's thesis.
  • 2017: The official site cites a DBSec publication on the CryFS construction.
  • 2024: CryFS 1.0.0 was published on the official GitHub releases page.
  • 2025: The 1.0.x and 2.0.0-alpha release lines were active on GitHub.

Related projects

  • The CryFS documentation contrasts its block-based metadata-hiding approach with file-based encrypted filesystems such as EncFS and gocryptfs, and the README points to SiriKali and KDE Plasma Vault as GUI front ends that can use CryFS.

Sicherheitslage

Risikostufe: orange

broad file, network, media, or database tool signal. infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • broad file, network, media, or database tool signal
  • infrastructure mutation or orchestration signal

Signale

  • text:cloud
  • text:encrypt

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 2 Plattformziele verfügbar.
  • Installiert mit 4 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 5 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
vaultdir/cryfs.config

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
cryfscliglobales Executable
cryfs-unmountcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version1.0.3
Manager aktualisiert2026-06-21
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/cryfs/cryfs

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cryfs
Version1.0.3
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cryfs
Homepagehttps://www.cryfs.org
Repositoryhttps://github.com/cryfs/cryfs
Upstream-Dokumentationhttps://www.cryfs.org/howitworks
LizenzLGPL-3.0-or-later
Quellarchivhttps://github.com/cryfs/cryfs/releases/download/1.0.3/cryfs-1.0.3.tar.gz
Zuletzt aktualisiert2026-06-21T20:12:11-04:00
Pulseupdated
Abhängigkeitenboost, fmt, libfuse@2, spdlog
Build-Abhängigkeitencmake, curl, pkgconf, python@3.14, range-v3
Bottleverfügbar (auf arm64_linux, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecryfs
Version Scheme0
Revision1
Head VersionHEAD
Requirements
  • linux
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Debian apt95%

cryfs 0.11.4-3

encrypt your files and store them in the cloud

https://www.cryfs.org/

sudo apt install cryfs
  • Section: utils
  • Architecture: amd64
  • 13 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Cryfs
Debian stable package indexes · deb.debian.org · Debian stable package indexes: cryfs from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Nix95%

cryfs

nix profile install nixpkgs#cryfs
  • normalized package name match
  • Abgeglichen nach: Cryfs
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/cr/cryfs/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Ubuntu apt95%

cryfs 0.11.4-1build5

encrypt your files and store them in the cloud

https://www.cryfs.org/

sudo apt install cryfs
  • Section: universe/utils
  • Architecture: amd64
  • 13 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Cryfs
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: cryfs from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz
dnf95%

cryfs 0.11.3-15.fc44

Cryptographic filesystem for the cloud

https://www.cryfs.org/

sudo dnf install cryfs
  • License: LGPL-3.0-only
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: cryfs
  • 14 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Cryfs
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: cryfs from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst
pacman95%

cryfs 1.0.3-5

Cryptographic filesystem for the cloud

https://www.cryfs.org

sudo pacman -S cryfs
  • License: LGPL-3.0-only
  • Architecture: x86_64
  • 8 Abhängigkeiten
  • normalized package name match
  • Abgeglichen nach: Cryfs
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: cryfs from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz
zypper95%

cryfs 1.0.3-1.6

Cryptographic filesystem for the cloud

https://www.cryfs.org/

sudo zypper install cryfs
  • License: LGPL-3.0-only
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: cryfs
  • 12 Abhängigkeiten
  • 2 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Cryfs
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: cryfs from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst
MacPorts95%

cryfs

sudo port install cryfs
  • normalized package name match
  • Abgeglichen nach: Cryfs
MacPorts ports tree · api.github.com · MacPorts ports tree: fuse/cryfs/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment