semvec/pypi-packages huggingface dataset:
django-fernet-encrypted-fields 0.3.1
This is inspired by django-encrypted-fields.
License: MIT

[![Pypi Package](https://badge.fury.io/py/django-fernet-encrypted-fields.png)](http://badge.fury.io/py/django-fernet-encrypted-fields)
[![Jazzband](https://jazzband.co/static/img/badge.svg)](https://jazzband.co/)

### Django Fernet Encrypted Fields

This package was created as a successor to [django-encrypted-fields](https://github.com/defrex/django-encrypted-fields).

#### Getting Started

```shell
$ pip install django-fernet-encrypted-fields
```

In your `settings.py`, set random SALT_KEY

```python
SALT_KEY = '0123456789abcdefghijklmnopqrstuvwxyz'
```

Then, in `models.py`

```python
from encrypted_fields.fields import EncryptedTextField

class MyModel(models.Model):
    text_field = EncryptedTextField()
```

Use your model as normal and your data will be encrypted in the database.

#### Rotating SALT keys

You can rotate salt keys by turning the `SALT_KEY` settings.py entry into a list. 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

```python
SALT_KEY = [
    'zyxwvutsrqponmlkjihgfedcba9876543210',
    '0123456789abcdefghijklmnopqrstuvwxyz'
]
```

#### Rotating SECRET_KEY

When you would want to rotate your `SECRET_KEY`, set the new value and put your old secret key value to `SECRET_KEY_FALLBACKS` list. That way the existing encrypted fields will still work, but when you re-save the field or create new record, it will be encrypted with the new secret key. (supported in Django >=4.1)

```python
SECRET_KEY = "new-key"
SECRET_KEY_FALLBACKS = ["old-key"]
```

If you wish to update the existing encrypted records simply load and re-save the models to use the new key.

```python
for obj in MyModel.objects.all():
    obj.save()
```

#### Available Fields

Currently build in and unit-tested fields. They have the same APIs as their non-encrypted counterparts.

- `EncryptedCharField`
- `EncryptedTextField`
- `EncryptedDateTimeField`
- `EncryptedIntegerField`
- `EncryptedFloatField`
- `EncryptedEmailField`
- `EncryptedBooleanField`
- `EncryptedJSONField`

### Compatible Django Version

| Compatible Django Version | Specifically tested |
| ------------------------- | ------------------- |
| `3.2`                     | :heavy_check_mark:  |
| `4.0`                     | :heavy_check_mark:  |
| `4.1`                     | :heavy_check_mark:  |
| `4.2`                     | :heavy_check_mark:  |
| `5.0`                     | :heavy_check_mark:  |
| `5.1`                     | :heavy_check_mark:  |