We are still actively working on the spam issue.
Difference between revisions of "Encryption"
(→tc-play) |
Toynbeeidea (talk | contribs) (→Why NaCL?) |
||
| Line 30: | Line 30: | ||
1. It's secure (Authentication, protection against timing attacks, etc..) | 1. It's secure (Authentication, protection against timing attacks, etc..) | ||
| − | 2. It's fast (RSA is very slow). | + | 2. It's fast (RSA is very slow, and the RSA was infiltrated by the [[NSA]]). |
3. The keys are only 256 bits (It's ECC), and it's as secure as RSA 3072. | 3. The keys are only 256 bits (It's ECC), and it's as secure as RSA 3072. | ||
Revision as of 20:06, 7 January 2015
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 is defunct as of 2014-5-28 after developer abandonment. Truecrypt was already of ambiguous trustworthiness, but this is the nail in its coffin. More here.
Contents
Windows
There is no 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 okay if you're hiding your hentai folder from l33t h4x0rs, your mom, normalfags and your idiot friends. Otherwise do not use, as all Microsoft products are backdoored.
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.
I Want to Implement Crypto Correctly in my Shitty App, What do I do?
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?
1. It's secure (Authentication, protection against timing attacks, etc..)
2. It's fast (RSA is very slow, and the RSA was infiltrated by the NSA).
3. The keys are only 256 bits (It's ECC), and it's as secure as RSA 3072.
Other Links
The Paranoid Crunchbang Security Guide -- Has tools and techniques that apply to other distros as well. Very good resource.
