Installer reop avec Homebrew

Liens du projet

• Page d'accueil

Commandes et alias

• reop

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

• 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.