bcrypt(1)

💖 bcrypt — the bcrypt(1) glow-up 💖

okay bestie, sit down, hydrate, because we're talking about bcrypt from the General Commands Manual and she is iconic. no cap.

---

✨ NAME ✨

bcrypt — blowfish file encryption 🐡🔐

---

✨ SYNOPSIS ✨

bcrypt [-orc][-sN] file ...

that's it. that's the whole vibe. literally one line and she ate. 💅

---

✨ DESCRIPTION ✨

so bcrypt encrypts and decrypts files using the blowfish algorithm. that's the main character job description, and she does it well. 🫶

encrypted files get saved with an extension of .bfe. any file that already ends in .bfe gets assumed to be encrypted with bcrypt, and she'll attempt to decrypt it. any other input file? yeah, that's getting encrypted. no thoughts, just encryption. ✨

⚠️ real talk tho: if you hand her more than one type of file, bcrypt will process all files which are the same as the first filetype given. so the first file you list basically decides the agenda for the whole group chat. 💀

by default, bcrypt will:

• compress input files before encryption 🗜️
• remove input files after they're processed (assuming they got processed successfully, king behavior) 🗑️
• overwrite input files with random data so nobody can do data recovery on your leftovers 🔥

passphrases may be between 8 and 56 characters. and listen, regardless of how long your passphrase is, the key gets hashed internally to 448 bits — that's the largest keysize supported by the blowfish algorithm. so she's giving maximum key energy no matter what. 👑

but still. it is still wise to use a strong passphrase. do not come in here with password123. i'm begging. 🙈

---

✨ OPTIONS ✨

• -o — print output to standard out. implies -r. 📤
• -c — DO NOT compress files before encryption. she's raw-dogging the compression step, respectfully. 🚫🗜️
• -r — DO NOT remove input files after processing. your originals stay. safe. sound. cozy. 🥰
• -sN — how many times to overwrite input files with random data before deleting. the default number of overwrites is 3. use -s0 to disable this feature entirely. no effect if -r is supplied. 🔁💀

---

✨ NOTES ✨

so the -o, -r, and -c options each have the opposite effects if the appropriate settings are altered from the defaults in config.h. i know. it's giving plot twist. 😭

to determine what effect each of these actually have on your system, just run bcrypt without any options. she'll tell you. she's transparent like that. ✨

encrypted files should be compatible between most systems. binary compatibility has been tested on all supported systems — no cap. there's a list of supported systems in the README file that was included with this software. go read it, bestie, it's right there. 📖

---

✨ BUGS ✨

Probably. 💀

if you find that it will not compile and run on your system, or that encrypted files are not compatible with other platforms, it's probably because I don't have access to the platform in question. not a skill issue, a hardware-access issue. 🙈

patches or access to an unsupported machine are welcome. genuinely. she's accepting gifts. 🎁

---

✨ AUTHOR ✨

johnny shelley <jshelley@cahaus.com>, <jshelley@ictransnet.com>

---

✨ DISTRIBUTION ✨

bcrypt includes Paul Kocher's implementation of the blowfish algorithm. 🐡

the version distributed with bcrypt has been altered. original sources are available from http://www.counterpane.com/bfsh-koc.zip

---

🌸 stay safe out there, encrypt your stuff, and never reuse a passphrase. mwah. 🫶

---

version 1.1 💖 10 September 2002 🎀 — yeah she's an older icon but she's still serving, and that's the whole bcrypt(1) situation, bestie. periodt. 💅✨🌈