@2
                            MMM
                        aMMMMMM
                      ZMMMMMMMMM0
                     @MMMMMMMMMMMM
                    rMMMMMMMMMMMMM
                   MMMMMMMMMMMMMMMM
               XMMMMMMMMMMMMMMMMMM
           @MMMMMMMMMMMMMMMMMM
         MMMMMMMMMMMMMMMMMMMMM
       ZMMMMMMMMMMMMMMMMMMMMMM
      :MMMMMMMMMMMMMMMMMMMMM0           My simple personal encryption tool...
     0MMMMMMMMMMMMMMMMMMMMM
    MMMMMMMMMMMMMMMMMMMMMM
   MMMMMMMMMMMMMMMMMMMMM
  MMMMMMMMMMMMMMMMMMM;
  MMMMMMMMMMMMMMMMMMM
  MMMMMMMMMMMMMMMMMMM
  MMMMMMMMMMMMMMMMMMM
  MMMMMMMMMMMMMMMMMMM
  MMMMMMMMMMMMMMMMMM8
  MMMMMMMMMMMMMMMMMM                i,
  MMMMMMMMMMMMMMM MM               MMMM
 MMMMMMMMMMMMMMB  MM i             MMM0
rMMMMMMMMMMMMMMMMrMMMMM           MMMM
 MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMX "Very well, very well, I'm prepared to be silent. I'll be a silent hallucination."
                                                                                 -- Bulgákov [The Master and Margarita]

...with my own "paranoid" cares.

Including:

    - Individual file encryption/decryption;

    - The possibility of cascading many ciphers
      (the cipher suite is configurable during the build);

    - Two ways of encrypting by cascading: single cascading, one-time pad based cascading;

    - HMACs for every block cipher supported. By using the following hash functions:
      SHA-224, SHA-256, SHA-384, SHA-512, SHA3-224, SHA3-256, SHA3-384, SHA3-512, Tiger, Whirlpool,
      Blake2s-256, Blake2b-512;

    - Block ciphers available in the following modes: CBC, OFB, CTR and GCM.

    - Bcrypt is also an option for password hashing (if you like it);

    - Configurable key derivation functions. The available KDFs are: HKDF, PBKDF2 and ARGON2I.

    - The possibility of encoding the encrypted data by using: UUEncode or Radix-64;

    - Some level of plausibly deniable encryption (by associating some "building block" commands);

    - Assuming your system is pretty bad configured and hacked...
      A device driver that avoids your files of being downloaded after decrypted;

    - This same device driver can avoid the replacement of your blackcat's binary copy for a tainted one;

    - If you are pretty paranoid, some cares for avoiding RAM swap issues that would leak some
      pretty sensitive information (depending on your requirements);

    - Debugging mitigation mechanism (if you are paranoid about it too);

    - Vpn-tunnel (socket level) with E2EE (by using a double ratchet-like mechanism or not);

    - Session key exchanging by using a modified Diffie-Hellman-Merkle scheme;

If you are interested in:

-> Read more about the build instructions in 'BUILD.txt'.

-> Read more about how to use the tool in 'doc/MANUAL.txt'.

-> Crypto experts, gurus or students, cypherpunks, cryptanalysts read 'chg/README'. You would be pretty valuable there.
   Thank you! :)

Any question or problem, you can open an issue at: <https://github.com/rafael-santiago/blackcat/issues> *

I have been using it in Linux, FreeBSD and NetBSD. Anyway, you should be able to build it in any decent Unix-like.

If you prefer, you can also use the basic features in Windows.

This is not for comercial use. This is personal, if you want to use it watch the restrictions to your
state of things, including your local country crypto regulation, the ciphers licenses too, etc.

Use this software at your own risk. I am not responsible for any misuse of it, including some kind of damage,
data loss, etc. Who knows your babysitter.


---

*[I am not a blasé peacock so I usually try to respond asap, thanks for your time!]