cryptobone(8)
π cryptobone β Secure Communication Under Your Control π
okay bestie, gather round, because this one is literally a whole vibe: it's cryptobone, manual section 8 (that's the sysadmin/daemon girlies section, iykyk). No cap, it's giving "your messages are safe and you didn't even have to think about it." π¦
β¨ SYNOPSIS β¨
/usr/bin/cryptobone2
that's it. that's the whole invocation. she's low maintenance, she's iconic. π
πΈ DESCRIPTION πΈ
so cryptobone2 is the graphical user interface (GUI) for a secure messaging system, and the entire point of her is that your message and your attachment are always encrypted β without ever making you do complex message key management. not even a little. she's built on top of a separate daemon, and together they serve ease-of-use and security through a genuinely novel approach to encryption key management. ate. π₯
while the message keys are secured by a daemon running on the Linux machine, you can get additional protection by using an external device to store the encryption keys. and that external device can be literally whatever works: another Linux computer dedicated to this one task, a Raspberry Pi, or honestly any device that can install the CryptoBone software. the range?? unmatched. π
here's the tea on how it actually works: the Crypto Bone secure messaging system automatically encrypts a message with a strong message key, which lives in the cryptobone daemon's data base for secrets. and bestie, except for an initial registration of a message key for a recipient, you do not need to remember any of these message keys that are in use β because the system updates keys when messages are sent out or received. it just handles it. main character energy fr fr. π
and the security model? only strongly end-to-end encrypted messages and attachments get sent out, via the safewebdrop transport mechanism. meanwhile, incoming messages that can't be decrypted with registered message keys are simply discarded. no crumbs, no leaks, no drama. π
β οΈ heads up though: in order to transfer encrypted messages, the system has to be set up with a working safewebdrop account β and that account must be used for this purpose only. (see https://safewebdrop.com) don't be out here sharing it with your other apps, okay? π
π OPTIONS π
- none
she takes no options. she needs no options. she simply is. π§
π FILES π
/usr/bin/cryptobone2
π SEE ALSO π
cryptoboned(8)
her daemon bestie. they're a package deal, your honor. π«Ά
β AUTHORS β
cryptobone2 has been written by Ralf Senderek <innovation@senderek.ie>. π
the core cryptographic library libcl.so which is used by the cryptobone daemon has been written by Peter Gutmann <pgut001@cs.auckland.ac.nz>. legends, both of them, no notes. π
π BUGS π
of course there aren't bugs β she's perfect, obviously π β but if you do find any, please sent them to innovation@senderek.ie.
yes bestie, it says "sent." we're keeping it exactly as written, that's part of the charm. π
and that's the whole page!! footer girlies, rise: this is cryptobone(8), credited to Ralf Senderek β and if your terminal is showing a date next to that, it's just the man page build date doing its thing. mwah. πβ¨π
π¦ where this page comes from
- fedora 43: cryptobone 2.0-3.fc43 Β· BSD-3-Clause and Sleepycat and OpenSSL
- fedora 43: cryptobone 2.2-3.fc43 Β· BSD-3-Clause and Sleepycat and OpenSSL
- fedora 44: cryptobone 2.0-5.fc44 Β· BSD-3-Clause and Sleepycat and OpenSSL
- fedora 44: cryptobone 2.2-3.fc44 Β· BSD-3-Clause and Sleepycat and OpenSSL
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms