Django-CryptographicFields
A Django app for using cryptography in Django Models. It support bi-directional cryptography.
Check out the documentation :- Django-CryptographicFields
Requirements
- Python (3.6+)
- Pycryptodome (3.9+)
- Django (3.0+)
- Timestring (1.6.0+) Mandatory if python < 3.7
Quick start
1.Install Django-CryptographicFields
Install Django CryptographicFields using PIP:-
pip install Django-CryptographicFields
2. Add "CryptographicFields" to your INSTALLED_APPS setting like this:
INSTALLED_APPS = [
...
'CryptographicFields',
]
3.Custom Encryption Key
Set custom Encryption Key in settings.py Make sure that key length is greater than or equal to 50 otherwise it will raise an error
CRYPTOGRAPHIC_KEY="your_key"
Creating Models using CryptographicFields
Cryptography by example
from CryptographicFields import fields
from django.db import models
class CryptogaphicModel(models.Model):
name=fields.CharField(max_length=120)
The data will now be automatically encrypted when saved to the database.& decrypted when data is retrieved.
Advantages over other projects:-
- Supports data retrival
- Supports custom query
- Supports Q() queries
- Supports Ordering data through python functions
- Supports Sorting data through python functions
- Supports 'startswith' lookups for all String Based Fields
- Supports 'date' lookup for Date,DateTime Fields
- Supports 'time' lookup for TimeField
For More Information check out the documentation :- Django-CryptographicFields
Metadata
Release files for Django-CryptographicFields 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Django-CryptographicFields-2.1.0.tar.gz | 7.6 kB | Without provenance | Details for Django-CryptographicFields-2.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| Django_CryptographicFields-2.1.0-py3-none-any.whl | Python 3 | none | any | Details for Django_CryptographicFields-2.1.0-py3-none-any.whl |
Total release size: 16.6 kB
Release files / Django-CryptographicFields-2.1.0.tar.gz
| Download URL | Django-CryptographicFields-2.1.0.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88c9de133dcb0dfb5f4ba95c48bdb691e89c1461905e444dde25827bf3637ee6
|
|
BLAKE2b-256 checksum How to use checksums |
f951163422c906a415dc105379e967927bff132775f631e73faa2e890fac0cd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.8.5
|
Release files / Django_CryptographicFields-2.1.0-py3-none-any.whl
| Download URL | Django_CryptographicFields-2.1.0-py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f3b65f640839e95cbb90ebc5ae88237853289697cc7e4ba79b535c13b3ad661
|
|
BLAKE2b-256 checksum How to use checksums |
b737802679adbeb65565f13ca4b0c6b95c68c7ca229a14cf38e47d7cafd333d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.8.5
|
Security for Django-CryptographicFields 2.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.