We are still actively working on the spam issue.
Difference between revisions of "Encryption"
| Line 1: | Line 1: | ||
'''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. | '''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. | ||
| + | == Windows == | ||
| + | === [http://www.truecrypt.org Truecrypt] === | ||
| + | A popular encryption solution for Windows. Allows full-disk encryption. | ||
| − | == | + | ==== Controversy ==== |
| − | + | === [https://web.archive.org/web/20130531062457/http://freeotfe.org/ FreeOTFE] === | |
| − | http:// | + | A now defunct project that allowed users to mount dm-crypt/LUKS volumes in Windows. Does not have signed drivers, so Microsoft makes it a pain in the ass to install and use. |
| + | == Linux == | ||
| + | === dm-crypt === | ||
| − | + | === [http://www.truecrypt.org Truecrypt] === | |
| + | ==== [https://github.com/bwalex/tc-play tc-play] ==== | ||
| + | A FOSS Truecrypt implementation to replace the official version. Supports most of Truecrypt's features. | ||
| + | == I Want to Implement Crypto Correctly in my Shitty App, What do I do? == | ||
| − | The important part with crypto is | + | The best and easiest to use public key crypto library is [http://nacl.cr.yp.to 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, [http://tobtu.com/decryptocat-old.php this] happens (you can't really have this problem with NaCl though). The other important part is ''always use a unique nonce''. |
| − | |||
| − | |||
| − | The other important part is | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | 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 [http://nacl.cr.yp.to/box.html this] page. | ||
| − | Why NaCL? | + | === Why NaCL? === |
1. It's secure (Authentication, protection against timing attacks, etc..) | 1. It's secure (Authentication, protection against timing attacks, etc..) | ||
Revision as of 02:36, 30 January 2014
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.
Contents
Windows
Truecrypt
A popular encryption solution for Windows. Allows full-disk encryption.
Controversy
FreeOTFE
A now defunct project that allowed users to mount dm-crypt/LUKS volumes in Windows. Does not have signed drivers, so Microsoft makes it a pain in the ass to install and use.
Linux
dm-crypt
Truecrypt
tc-play
A FOSS Truecrypt implementation to replace the official version. Supports most of Truecrypt's features.
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).
3. The keys are only 256 bits (It's ECC), and it's as secure as RSA 3072.
4. It isn't a bloated pile of crap filled with insecure ciphers (OpenSSL)
