carnage / doctrine-encrypted-column Goto Github PK

Ideally the stored value should contain metadata about how it was encrypted; this allows for easy upgrades, without this if something needs to change in the implementation(s), users are stuck until they decrypt/reencrypt their whole db.

The encryption service will then need to check the metadata to know how to decrypt and in the event that it used a method which is out dated reencrypt on save regardless of change to the data.

Depends on #3

Libraries targeted:
Using none standard AES in ECB mode:
https://github.com/vmelnik-ukraine/DoctrineEncryptBundle
https://github.com/reprovinci/doctrine-encrypt
https://github.com/51systems/doctrine-encrypt
https://github.com/juliencharrel/DoctrineEncryptBundle
https://github.com/ambta/DoctrineEncryptBundle (has other modes which includes standard ECB mode aes)

Please feel free to add a comment linking to your current library and I'll attempt to provide a migration path.

Halite version 5 was released today, which contains a few security improvements and may be worth the effort to upgrade to v5.

https://github.com/paragonie/halite/releases/tag/v5.0.0

(You're receiving this issue because Packagist says you depend on Halite.)

Make a pop-art version of the Doctrine logo by running it through AES in ECB mode.