issues
search
jazzband
/
django-fernet-encrypted-fields
MIT License
47
stars
10
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Encrypted fields should not assume None is an allowed value
#21
scottpashley
closed
3 weeks ago
0
Is there a guideline to migrate from obsoleta django-encrypted-fields?
#20
domdinicola
opened
5 months ago
0
Improve CI setup, add testing with Django 5 and Python 3.11
#19
artursmet
closed
7 months ago
1
Update ci and code
#18
sevdog
opened
7 months ago
4
Implement Jazzband guidelines for django-fernet-encrypted-fields
#17
jazzband-bot
opened
1 year ago
2
Adding typings to codebase
#16
faradayyg
opened
1 year ago
5
Fix minimum django version to 3.2
#15
frgmt
closed
1 year ago
0
Add support for encrypted JSON fields
#14
faradayyg
closed
1 year ago
1
Updating Django's SECRET_KEY makes encrypted fields inaccessible
#13
hendrikschneider
opened
1 year ago
7
Issues with lookups against encrypted fields
#12
alien8ion
opened
2 years ago
2
Fix #10
#11
frgmt
closed
2 years ago
13
I got KeyError: TextField when I tried using EncryptedIntegerField
#10
Ali-Javanmardi
closed
2 years ago
3
Hendrikschneider patch 1
#9
hendrikschneider
closed
2 years ago
0
setup github actions with black, flake8, testing and coverage
#8
hendrikschneider
closed
2 years ago
7
Joining Jazzband
#7
hendrikschneider
closed
1 year ago
12
Reasons for not leaving SECRET_KEY used as default
#6
jpic
closed
2 years ago
1
Fix for Error saving model in django admin
#5
StevenMapes
closed
2 years ago
0
Error saving model in django admin
#4
victorouttes
closed
2 years ago
4
Updated README.md with rotating SALT documentation
#3
StevenMapes
closed
2 years ago
1
Feature Request: Add support for rotating the salt
#2
StevenMapes
closed
2 years ago
1
Add in support for rotating the salt but allow older records to still be read
#1
StevenMapes
closed
2 years ago
1