# Install reop with Homebrew Encrypted keypair management. Version 2.1.1 via Homebrew; verified 2026-06-27. ## Install ```sh sudo av install brew:reop ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install reop ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:reop - **Package manager:** Homebrew - **Package manager page:** - **Version:** 2.1.1 - **Source summary:** Encrypted keypair management - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** ISC - **Source archive:** - **Last updated:** 2026-06-27T18:58:57-04:00 - **Generated:** 2026-07-08T18:08:21+00:00 ## Executables - reop (cli) - reop (alias) ## Dependencies - libsodium ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 2.1.1 - Package-manager updated: 2026-06-27 - Local data: ok - Upstream repository: https://web.archive.org/web/20251224210131/https://flak.tedunangst.com/post/reop - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage reop, short for reasonable expectation of privacy, is a minimalist command-line tool for signatures and file encryption. ### Project history The README frames reop as an extension of ideas from signify rather than an OpenPGP clone. It was written by Ted Unangst and uses NaCl/libsodium primitives for signing and encryption. ### Adoption history reop was adopted mainly by BSD and Homebrew-style packaging channels as a compact alternative to larger tools such as GnuPG or OpenSSL for simple signing and encryption workflows. Homebrew packages version 2.1.1 from a ports distfile and marks it unmaintained. ### How it is used The manual documents modes for generating keys, encrypting, decrypting, signing, and verifying. It searches ~/.reop for default key files named seckey, pubkey, and pubkeyring, while command-line options can point to explicit key and message files. ### Why package nerds care reop is notable to package maintainers because it is a small cryptographic CLI with a tight dependency story around libsodium, explicit limits, a simple trust model, and source releases that remain useful even without broad ecosystem adoption. ### Timeline - 2014: reop.1 carries an Mdoc date of March 16, 2014. - 1.0: README history records the initial release. - 1.1.1: README history records binary encrypted messages via the -b option. - 2.1: README history records a more secure encrypted message format as the default. - 2.1.1: Homebrew packages this version from the ports distfile. ### Related projects - The README names signify as an influence and libsodium/NaCl as the cryptographic foundation. ### Sources - GitHub unkaktus/reop README. - Homebrew formula metadata for reop. - reop README and reop.1 from the 2.1.1 source tarball. ## Security Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool signal ## 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. ## Credential files - Unix: ~/.reop/seckey, ~/.reop/pubkey, ~/.reop/pubkeyring ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** reop - **Version Scheme:** 0 - **Revision:** 1 - **Bottle Stable Root URL:** - **Deprecated:** yes - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Related links - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Archive and compression packages](https://www.automicvault.com/pkg/archive-compression-tools/) - Matched archive or compression metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [skm](https://www.automicvault.com/pkg/brew/skm/) - Shares av.db curated category or tags: cli, key-management, security. - [gpa](https://www.automicvault.com/pkg/brew/gpa/) - Shares av.db curated category or tags: cli, key-management, security. - [gpg-tui](https://www.automicvault.com/pkg/brew/gpg-tui/) - Shares av.db curated category or tags: cli, key-management, security. - [encfs](https://www.automicvault.com/pkg/brew/encfs/) - Shares av.db curated category or tags: cli, encryption, security. - [enchive](https://www.automicvault.com/pkg/brew/enchive/) - Shares av.db curated category or tags: cli, encryption, security. - [git-crypt](https://www.automicvault.com/pkg/brew/git-crypt/) - Shares av.db curated category or tags: cli, encryption, security. - [git-remote-gcrypt](https://www.automicvault.com/pkg/brew/git-remote-gcrypt/) - Shares av.db curated category or tags: cli, encryption, security. - [gnupg](https://www.automicvault.com/pkg/brew/gnupg/) - Shares av.db curated category or tags: cli, encryption, key-management, security. - [pwsafe](https://www.automicvault.com/pkg/brew/pwsafe/) - Security-sensitive metadata or terminology overlaps. Shared terms: cli, encrypted, encryption, management, security. ## Combined YAML source View the package source record on GitHub. [combined/reop.yml](https://github.com/automic-vault/db/blob/main/combined/reop.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - cross-ecosystem install command graph