v0.18.2

Fixes log scrubbing encoding issue #80

v0.18.1

• Force input to be a string. Fixes #76

v0.18.0

• Adds encrypt_table! class methods to encrypted models. This allows you to encrypt a table which contains existing data.

v0.17.0

• Adds the encoding option to crypt_keeper which allows you to force a string encoding on the data before encryption and after decryption. This is useful when using multibyte strings.

v0.16.1

Note: This update deprecates the AES and MySQL AES encryptors, which are now referred to as Legacy. A future release will completely remove the Legacy AES encryptors in favor of a more secure implementation of the encryptors. Data will need to be migrated to the new encryption using bin/crypt_keeper.

• MySQL AES and Ruby AES Passphrases are now derived using PBKDF2 hashing for enhance security. Because of this change, the above encryptors now requires a salt param in addition to the key. The salt it used when hashing the passphrase to ensure a unique key is used when encrypting data. The Armor gem is used to accomplish this.
• The AES provider internals were replaced with the AES gem.
• Migration paths for Legacy AES and Legacy MySQL were added to bin/crypt_keeper
• Added the PostgreSQL PGP Public Key encryptor
• Added the search_by_plaintext for searching encrypted data
• Log subscribers are now more aggressive to ensure searches do not leak keys or plaintext
• Bugfix for #35
• Encryptors now use serializers instead of callbacks

v0.15.0.pre

• Rails 3.0 support has been removed. The minimum version is now 3.1.
• Feature: Added search interface #53
• Bugfix: Do not attempt to encrypt/decrypt empty or nil values. Most of the underlining encryption technologies do not allow empty values. #57

v0.14.0.pre

• Switch from using ActiveRecord callbacks to serializers