Change the key generator when :iv is specified to use a Digest of the
secret
Change the key initialization rutine. No salt added, need to verify this
is still safe, seems it should be, since encrypting multiple strings
with same key but different iv should be OK
Revert the key without a salt. This is a bad idea. Hiding details out of
the programmer is a good idea as long as the best route is taken. This
was not however the case, and taking of the salt is not secure.
Fix Readme
Added salts and IV. This is what attr_encrypted will use by default
Change versioning to reset for new project. Also updated the README file
to use markdown instead. I will also publish the gem to rubygems as its
much easier to version it than using github and bundler
Change gem name so it does not conflict with encryptor
Small formatting issue
Merge branch 'master' into p-danpal-encryptor-merge

Merge brings in changes that fixes small issues with unit tests. It also brings
in the new CompatibilityTest unit test class which no longer passes since API
in this branch requires :salt option. These failing tests are temporarily
disabled until the API is made backwards-compatible.
New compatibility tests for encryption/decryption with salt
Reindented code for consistency
Introduce backwards compatibility with old version of Encryptor API

Change introduces backwards compatibility by switching into "legacy" mode if no
:salt option is provided to the "crypt" method. Change also ports over the
original test case, separates out common test helpers into OpenSSLHelper, and
enables compatibility tests than now pass since the API supports both legacy
and salted modes of operation.