# bcrypt mit Homebrew, dnf, MacPorts installieren

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

## Installation

```sh
sudo av install brew:bcrypt
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install bcrypt
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install bcrypt
```

  Evidenz: MacPorts ports tree: security/bcrypt/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- dnf (92%):

```sh
sudo dnf install bcrypt
```

  Evidenz: Fedora Rawhide package metadata: bcrypt from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst

## Paketfakten

- **Paketschlüssel:** brew:bcrypt
- **Paketmanager:** Homebrew
- **Version:** 1.1
- **Quellzusammenfassung:** Cross platform file encryption utility using blowfish
- **Homepage:** <https://bcrypt.sourceforge.net/>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- bcrypt (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.1
## Projektgeschichte und Nutzung

bcrypt is a small cross-platform command-line file encryption utility built around the Blowfish block cipher, not the later password-hashing scheme that shares the same name. Its public SourceForge page and bundled README describe a Unix-style tool that encrypts files to .bfe files, optionally compresses input, and securely overwrites originals before removal.

### Projektgeschichte

Johnny Shelley published bcrypt 1.1 in 2002 under a BSD-style license. The project page ties the tool directly to Bruce Schneier's 1993 Blowfish algorithm and Paul Kocher's public Blowfish implementation, with local changes shipped in the bcrypt source archive.

The 1.1 release notes emphasize portability work: bcrypt had been tested across FreeBSD, OpenBSD, Linux, Cygwin, Win32, Solaris, Mac OS X 10.1 Server, HP-UX, Alpha, MIPS, PPC, SPARC, and other systems. The same notes warn users upgrading from 1.0 on some unsupported architectures to decrypt and re-encrypt files because early portability bugs could affect compatibility.

### Adoptionsgeschichte

bcrypt's adoption pattern is typical of early-2000s security utilities: a small upstream tarball, a SourceForge homepage, and packaging by Unix-like distributions for users who wanted a simple local file encryptor. The Homebrew, Fedora, and MacPorts package names preserve that utility even though modern searches for 'bcrypt' usually find password hashing libraries instead.

### Wie es verwendet wird

The documented interface is deliberately small: run bcrypt on one or more files, producing .bfe encrypted files; run it again on .bfe input to decrypt. Options control stdout output, compression, removal of input files, and the number of overwrite passes before deletion.

### Warum Paket-Nerds sich dafür interessieren

For package historians, bcrypt is interesting because it is a name collision frozen in package indexes: this package is a Blowfish file-encryption CLI, while 'bcrypt' is now better known as a password hashing algorithm. It also captures a period when secure deletion, endian portability, source tarballs, GPG signatures, and cross-architecture binary compatibility were front-and-center concerns for small security packages.

### Zeitleiste

- 1993: Bruce Schneier publishes the Blowfish algorithm, which bcrypt later uses.
- 2002: bcrypt 1.1 is released by Johnny Shelley with bug fixes, broader operating-system support, better speed, and lower memory use.
- 2000s-2020s: Unix package managers continue carrying bcrypt as a niche file-encryption utility.

### Related projects

- Blowfish is the cipher family named by the bcrypt documentation as the cryptographic basis for the tool.
- zlib is the compression dependency documented for the source build.
- Modern bcrypt password-hashing libraries are related mainly by name and Blowfish lineage; they are not the same package or interface.

### Quellen

- <https://bcrypt.sourceforge.net/>
- <https://bcrypt.sourceforge.net/bcrypt-1.1.tar.gz>
- source_facts.package-manager


## Sicherheitshinweise

broad file, network, media, or database tool signal.

- **Geiger-Risiko:** blue / mittel
- broad file, network, media, or database tool signal

## Andere Paketmanager-Einträge

- dnf - bcrypt - 1.1-41.fc45: normalized package name match | Fedora Rawhide package metadata: bcrypt from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/07190dc5ae9f35ae73866675fed6d95fe6e8d9fe22c9d7cdf85862cb2ed24a4c-primary.xml.zst | File encryption utility | http://bcrypt.sourceforge.net/
- MacPorts - bcrypt: normalized package name match | MacPorts ports tree: security/bcrypt/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/bcrypt.yml](https://github.com/mxcl/pkgdb/blob/main/combined/bcrypt.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph