This is a bug fix for issue #4 where Django Admin raises an exception when saving Encrypted fields as the value is not encrypted at the time of the clean process.
This PR sets a semaphore property which is checked within the to_python method allowing the decryption to be skipped. It then removes the semaphore property to clean up the field
I've updated the README.md file with an explanation on how to config the multiple SALTs and how to update all records within a model that uses encrypted fields.
This commit adds in support for the SALT to be rotated by defining a list of salts within settings.py where the newer salts are added to the start.
The first key will be used to encrypt all new data, and decryption of existing values will be attempted with all given keys in order. This is useful for key rotation: place a new key at the head of the list for use with all new or changed data, but existing values encrypted with old keys will still be accessible
This is based of django-fernet-fields which is a dead package but has some useful features such as this to allow the salt to be rotated in the future for a stronger salt.
```
SALT_KEY = [
'my-newer-salt',
'the-original-salt'
]
```
