New answers tagged openssl
It comes from the (somehow abusive) software simplifications when computing the CRT. Here is the simplified code (as in pkcs#1 v2.1) m1 = (c^dP) % p m2 = (c^dQ) % q h = (q_inv*(m1 - m2)) % p m = m2 + h*q Agggh, Outch. when m2 > m1, we enter the realm of negative numbers unfriendly to unsigned crypto libraries. Then many authors suggested this ...
Not a definite answer but too much for comments: That help msg shows that OpenSSL on OSX is an old version (<= 0.9.8) before GCM was added. (Probably =; 0.9.7 end-of-lifed around 2008. -salt has been the default since about 2004 so anyone who claims you need to specify it should be treated very skeptically.) You could add HMAC on top of AES-CBC ...
Why not using VeraCrypt http://en.wikipedia.org/wiki/VeraCrypt, which is a successor of the famous discontinuited TrueCrypt. VeraCrypt is open source, and was developped by M. Idrassi an crypto-expert, take a look at https://github.com/veracrypt/VeraCrypt . There was controversy about the TrueCrypt, mysterious stoping. VeraCrypt corrected some know flaws and ...
Have you tried eCryptfs? It's the default encryption method of home folder in Ubuntu. You should give a try!
In theory, aes-256-cbc cipher is safe for encrypting building blocks of the file you are trying to encrypt, with appropriate padding and IV random generation. However, you may wish to note that: you need to securely erase the unencrypted file after you encrypt it. rm -rf filename does not erase the cleartext file, use srm instead.
Top 50 recent answers are included