Django-x509

Latest version: v1.2

Safety actively analyzes 723144 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 6

0.9.1

--------------------------

- [deps] Updated cryptography minimum version to 3.2 for security reasons
The version range has also been relaxed to avoid having to update it too
often, future versions up to but excluding 4.0 will be accepted
- [fix] Removed ``static()`` call from admin media
- [tests] Updated openwisp-utils[qa] to 0.7

0.9.0

--------------------------

Changes
~~~~~~~

- Models: updated ``max_length`` of ``common_name`` (``Ca`` and ``Cert``)
to from ``63`` to ``64``, following conventions about maximum length of
common names and hostnames

0.8.0

--------------------------

Features
~~~~~~~~

- Added swappable models, improved extensibility
- Improved documentation on `how to extend django-x509
<https://github.com/openwisp/django-x509#extending-django-x509>`_

Changes
~~~~~~~

- **Breaking change**: systems using django-x509 as a library must set
``DJANGO_X509_CA_MODEL`` & ``DJANGO_X509_CERT_MODEL`` values in their
settings.py when upgrading or an exception like the following one will
be raised:

``django.core.exceptions.ImproperlyConfigured: Could not find
django_x509.Ca!``

- Added support for django 3.1
- Added support for cryptography 3.0.0

Bugfixes
~~~~~~~~

N/A

0.7.0

--------------------------

- Added possibility to renew CAs and certificates
- Updated dependency to support cryptography 2.9

0.6.2

Not secure
--------------------------

- Switched back to jsonfield

0.6.1

Not secure
--------------------------

- Ensured RFC5280 datetime standard
- Increased maximum length of x509 serial number to 48
- jsonfield2 version set to >=3.1.0,<4.0.0

Page 2 of 6

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.