Encryption

Encryption is the art of encoding messages in a way that only the intended, authorized person may read it. According to Edward Snowden, strong, tested cryptographic encryption systems were said to be one of the few remaining things that work (i.e. haven't been compromised by the NSA), and that people can still rely on.

Truecrypt has now been audited and is safe to use, so long as you read this page in its entirety.'

Windows

There is no seriously safe option for serious bulk symmetric encryption on Windows anymore. Windows is as far deep inside the botnet as Mac OS X and must not be used if you have any need of data security. BitLocker is only acceptable if you're hiding basic files (read: anything that's not cat photos.) VeraCrypt and TrueCrypt are options that will help you from anything that's not LE, as all Microsoft products are backdoored.

Bitlocker has been broken since 2010.

OS X

Again, much like Windows, there is no safe option for bulk symmetric encryption on OS X. OS X contains backdoors like any other non free operating system. FileVault, VeraCrypt and TrueCrypt are all only acceptable if you're hiding files from thieves and other such people. OS X is backdoored by the NSA.

GNU/Linux

dm-crypt

dm-crypt + LUKS is the recommended encryption solution for GNU/Linux. It comes with the kernel. Since version 1.6, cryptsetup supports TrueCrypt containers natively, so there's no need to install TrueCrypt or tc-play.

tc-play

A FOSS Truecrypt implementation to replace the official version. Supports most of Truecrypt's features. Nowadays useful only for reading your Truecrypt volume and migrating it to dm-crypt.

VeraCrypt

TrueCrypt's successor. Is cross-platform and has a TrueCrypt compatibility mode for those with old TC disks.

OpenSSL File Encryption

• Encoding: $ openssl enc -aes-256-cbc -in plaintext.file -out cyphertext.file
• Decoding: $ openssl enc -aes-256-cbc -d -in cyphertext.file > plaintext.file

You will be prompted for a password.

Cryptology in Applications

The best and easiest to use public key crypto library is NaCl. Don't even try creating your own crypto algorithm or using another shitty library. The important part with crypto is always use enough randomness in your keys. If you don't, this happens (you can't really have this problem with NaCl though). The other important part is always use a unique nonce.

NaCl is real easy to use, just use crypto_box_keypair() to generate a public/private keypair, use crypto_box() to encrypt data and use crypto_box_open() to decrypt it (This is the only function that you need to check the return value, it returns -1 if the decryption failed). Why does crypto_box() use your private key to encrypt a message you ask? That's so the other can check if that encrypted message really came from you, the same reason why crypto_box_open() takes the public guy of the guy who sent you the encrypted data.

If you have a grain of intelligence, before using NaCl for anything you will read everything on the website, especially this page.

- Why NaCl?

- It's secure (Authentication, protection against timing attacks, etc..)

- It's fast (RSA is very slow, and the RSA was backdoored by the NSA).

- The keys are only 256 bits (It's ECC), and it's as secure as RSA 3072.

Other Links

The Paranoid Crunchbang Security Guide This Crunchbang forum post has tools and techniques that specifically apply to #!++, but easily applies to other distros as well. Very good resource.

This is an explanation into why TrueCrypt is still safe to use, as well as this.

Here and here are both links to TrueCrypt's spiritual successor, VeraCrypt.

Bitlocker and FileVault links are here if you are absolutely retarded and haven't read a single thing on this page. Cat photos only.

Also check Fucko for other tips.