From your "how to use" page:<p><pre><code> # echo mysupersecretkey > /backups/key
# openssl enc -aes-256-cbc -salt -in fullbackup.tar.gz \
-out fullbackup.tar.gz.enc -pass file:/backups/key
</code></pre>
Please don't do this. openssl -aes-256-cbc is <i>not</i> a strong key derivation algorithm, so you need to use keys with much higher entropy (dd if=/dev/random of=/backups/key); an attacker can run through a dictionary of common passwords ridiculously quickly, thousands of times faster than when you're using a proper key derivation algorithm, e.g. bcrypt/scrypt/PBKDF2 to generate the key. If you do want to derive it from something akin to a password.<p>More seriously, openssl -aes-256-cbc does not do any integrity protection; in fact, an attacker can more or less flip any bits of his choosing in the ciphertext to flip those same bits in the plaintext. (Yes, I'm aware it's a tiny bit more complicated than that.)<p>It <i>is</i> possible to fix both of the above, but may I recommend gpg --symmetric as a simple and reasonably secure alternative?