django-bcrypt
django-bcrypt makes it easy to use bcrypt to hash passwords with Django.
Installation and Usage
Install the package with pip and Mercurial or git:
pip install -e hg+http://bitbucket.org/dwaiter/django-bcrypt#egg=django-bcrypt # or ... pip install -e git://github.com/dwaiter/django-bcrypt.git#egg=django-bcrypt
Add django_bcrypt to your INSTALLED_APPS.
That’s it.
Any new passwords set will be hashed with bcrypt. Old passwords will still work fine.
Configuration
You can set BCRYPT_ROUNDS in settings.py to change the number of rounds django-bcrypt uses. The default is 12.
You can change the number of rounds without breaking already-hashed passwords. New passwords will use the new number of rounds, and old ones will use the old number.
Acknowledgements
This is pretty much a packaged-up version of this blog post for easier use.
It also depends on the py-bcrypt library.
Release files for django-bcrypt 0.9.2
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 | |
|---|---|---|---|---|
| django-bcrypt-0.9.2.tar.gz | 4.0 kB | Without provenance | Details |
Release files / django-bcrypt-0.9.2.tar.gz
| Download URL | django-bcrypt-0.9.2.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78998fc296232df1c4f61143b06460c0d1fff6f1e4e7a9e41aabad8a6fe3d751
|
|
BLAKE2b-256 checksum How to use checksums |
2205c18aa9c41fc6efec2cc1662e0f6bb0fb81a7bbf52d14f392b661e28c9464
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-bcrypt 0.9.2
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.
