django-ca

Django app providing a Certificate Authority

GPL-3.0 License

Downloads
3.9K
Stars
133
Committers
12
django-ca - 1.12.0 (2019-04-02)

Published by mathiasertl over 5 years ago

  • Fix traceback when a certificate that does not exist is viewed in the admin interface.
  • Add support cryptography 2.5 and 2.6.
  • Start using Django storage backends for files used by django-ca. This allows you to store files on a shared storage system (e.g. one from django-storages to support a redundant setup.
  • Add support for PrecertPoison and OCSPNoCheck extensions.
  • Implement the PrecertificateSignedCertificateTimestamps extension, currently can only be used for reading existing certificates.
  • Optimize PrecertificateSignedCertificateTimestamps in Django admin view.
  • Make sure that all extensions are always hashable.
  • Switch Docker image to Alpine Linux 3.9.
  • BACKWARDS INCOMPATIBLE: Drop support for Python 3.4.
  • BACKWARDS INCOMPATIBLE: Drop support for Django 2.0.
  • BACKWARDS INCOMPATIBLE: Drop support for cryptography 2.1.
  • DEPRECATION NOTICE: This is the last release to support cryptography 2.2.
  • DEPRECATION NOTICE: This is the last release to support idna 2.6.

Django File storage API

django-ca now uses the File storage API to store CA private keys as well as files configured for OCSP views. This allows you to use different storage backends (e.g. from django-storages to store files on a filesystem shared between different servers, e.g. to provide a redundant setup.

NOTE: The switch does require some manual intervention when upgrading. The old way of storing files is still supported and will continue to work until version 1.14. Please see the upgrade notes for information on how to upgrade.

  • Use file storage API for reading/writing private keys of CAs.
  • Use file storage API for reading the responder key and certificate for OCSP.
  • New settings CA_FILE_STORAGE and CA_FILE_STORAGE_KWARGS to configure file storage.

OCSP

  • Reimplement OCSP using cryptography, used only if cryptography>=2.4 is installed.
  • django_ca.views.OCSPBaseView.responder_key may now also be a relative path to be used with the Django storage system.
  • django_ca.views.OCSPBaseView.responder_cert may now also be a relative path to be used with the Django storage system.
  • django_ca.views.OCSPBaseView.responder_cert may now also be a pre-loaded certificate. If you still use cryptography<2.4 use a oscrypto.asymmetric.Certificate, for newer versions you must use a cryptography.x509.Certificate.
  • Fix log output string interpolation issue in OCSP responder.
django-ca - 1.11.0 (2018-12-29)

Published by mathiasertl almost 6 years ago

  • Remove colons from CA private keys (fixes #29).
  • Filenames for downloading certificates are based on the CommonName (fixes #53).
  • Fix certificate bundle order (fixes #55).
  • Management commands dump_ca and dump_cert can now dump whole certificate bundles.
  • New setting CA_DEFAULT_KEY_SIZE to configure the default key size for new CAs.
  • Fix display of the NameConstraints extension in the admin interface.
  • Further optimize the Docker image size (~235MB -> ~140MB).

Deprecation Notices

This release will be the last release to support some software versions:

  • This will be the last release that supports for Python 3.4 (see Status of Python branches).
  • This will be the last release that supports for Django 2.0 (see Supported Versions).
  • This will be the last release that supports cryptography 2.1.

Python API

Testing

  • Add cryptography 2.4.2 to the test-suite.
  • Add the docker_test setup.py command to test the image using various alpine-based images.
  • Test for certificates that are not yet valid.
  • The child CA used for testing now contains more extensions.
  • Freeze time in some test cases to avoid test failures when certificates eventually expire.
  • Test some documentation pages, to make sure they are actually correct.
django-ca - 1.10.0

Published by mathiasertl almost 6 years ago

  • New dependency: django-object-actions.
  • Add ability to resign existing certificates.
  • Management command list_cas now optionally supports a tree view.
  • Use more consistent naming for extensions throughout the code and documentation.
  • Renamed the --tls-features option of the sign_cert command to --tls-feature, in line with the actual name of the extension.
  • Allow the TLSFeature extension in profiles.
  • Add link in the admin interface to easily download certificate bundles.
  • Support ECC private keys for new Certificate Authorities.
  • Store CA private keys in the more secure PKCS8 format.
  • The Certificate change view now has a second "Revoke" button as object action next to the "History" button.

Python API

  • Add the Python API as a fully supported interface to django-ca.
  • New module django_ca.extensions to allow easy and consistent handling of X509 extensions.
  • Fully document various member attributes of CertificateAuthority and Certificate, as well Subject and as all new Python code.
  • The parameters for functions in CertificateManager and CertificateAuthorityManager were cleaned up for consistent naming and so that a user no longer needs to use classes from the cryptography libary. Parameters are now optional if default settings exist.
  • Variable names have been renamed to be more consistent to make the code more readable.

Testing

  • Also test with Python 3.7.0.
  • Add configuration for tox.
  • Speed up test-suite by using force_login() and PASSWORD_HASHERS.
  • Load keys and certs in for every testcase instead for every class, improving testcase isolation.
  • Add two certificates that include all and no extensions at all respectively to be able to test edge cases more consistently and thoroughly.
  • Add function cmd_e2e to call manage.py scripts in a way that arguments are passed by argparse as if they where called from the command-line. This allows more complete testing including parsing commandline arguments.
  • Error on any warnings coming from django-ca when running the test-suite.
django-ca -

Published by mathiasertl about 6 years ago

  • Allow the creation of Certificates with multiple OUs in their subject (command-line only).
  • Fix issues with handling CAs with a password on the command-line.
  • Fix handling of certificates with no CommonName and/or no x509 extensions.
  • Add support for displaying Signed Certificate Timestamps (SCT) Lists, as described in RFC 6962, section 3.3.
  • Add limited support for displaying Certificate Policies, as described in RFC 5280, section 4.2.14 and RFC 3647.
  • Correctly display extensions with an OID unknown to django-ca or even cryptography.
  • Properly escape x509 extensions to prevent any injection attacks.
  • Django 2.1 is now fully supported.
  • Fix example command to generate a CSR (had a stray '/').
  • Run test-suite with template debugging enabled to catch silently skipped template errors.

Docker

  • Base the Docker image on python:3-alpine (instead of python:3), yielding a much smaller image (~965MB -> ~235MB).
  • Run complete test-suite in a separate build stage when building the image.
  • Provide uwsgi.ini for fast deployments with the uwsgi protocol.
  • Add support for passing additional parameters to uWSGI using the DJANGO_CA_UWSGI_PARAMS environment variable.
  • Create user/group with a predefined uid/gid of 9000 to allow better sharing of containers.
  • Add /usr/share/django-ca/ as named volume, allowing a setup where an external webserver serves static files.
  • Add documentation on how to run the container in combination with an external webserver.
  • Add documentation on how to run the container as a different uid/gid.
django-ca -

Published by mathiasertl about 6 years ago

NOTE: This version was actually released on 2018-07-08, but the GitHub release was omitted.

  • Add Django signals to important events to let users add custom actions (such as email notifications etc.) to those events (fixes #39).
  • Provide a Docker container for fast deployment of django-ca.
  • Add the CA_CUSTOM_APPS setting to let users that use django-ca as a standalone project add custom apps, e.g. to register signals.
  • Make the otherName extension actually usable and tested (see #47)
  • Add the smartcardLogon and msKDC extended key usage types. They are needed for some AD and OpenLDAP improvements (see #46)
  • Improve compatibility with newer idna versions (".com" now also throws an error).
  • Drop support for Django 1.8 and Django 1.10.
  • Improve support for yet-to-be-released Django 2.1.
  • Fix admin view of certificates with no subjectAltName.
django-ca - 1.7.0 (2017-12-14)

Published by mathiasertl almost 7 years ago

  • Django 2.0 is now fully supported. This release still supports Django 1.8, 1.10 and 1.11.
  • Add support for the tlsFeature extension.
  • Do sanity checks on the "pathlen" attribute when creating Certificate Authorities.
  • Add sanity checks when creating CAs:
    • When creating an intermediate CA, check the pathlen attribute of the parent CA to make sure that the resulting CA is not invalid.
    • Refuse to add a CRL or OCSP service to root CAs. These attributes are not meaningful there.
  • Massively update documentation for the command-line interface.
  • CAs can now be identified using name or serial (previously: only by serial) in CA_OCSP_URL.
  • Make fab init_demo a lot more useful by signing certificates with the client CA and include CRL
    and OCSP links.
  • Run fab init_demo and documentation generation through Travis-CI.
  • Always display all extensions in the django admin interface.
  • NameConstraints are now delimited using a , instead of a ;, for consistency with other
    parameters and so no bash special character is used.

Bugfixes

  • Check for permissions when downloading certificates from the admin interface. Previously, users without admin interface access but without permissions to access certificates, where able to guess the URL and download public keys.
  • Add a missing migration.
  • Fix the value of the crlDistributionPoints x509 extension when signing certificates with Python2.
  • The Content-Type header of CRL responses now defaults to the correct value regardless of type (DER or PEM) used.
  • If a wrong CA is specified in CA_OCSP_URLS, an OCSP internal error is returned instead of an uncought exception.
  • Fix some edge cases for serial conversion in Python2. Some serials where converted with an "L" prefix in Python 2, because hex(0L) returns "0x0L".
django-ca - 1.6.3

Published by mathiasertl about 7 years ago

  • Fix various operations when USE_TZ is True.
  • CA keys are no longer stored with colons in their filename, fixing init_ca under Windows.
  • Email addresses are now independently validated by validate_email. cryptography 2.1 no longer
    validates email addresses itself.
  • Require cryptography>=2.1. Older versions should not be broken, but the output changes
    breaking doctests, meaning they're no longer tested either.
django-ca - version 1.6.2

Published by mathiasertl over 7 years ago

  • No longer require a strict cryptography version but only >=1.8. The previously pinned version is incompatible with Python 3.5.
  • Update requirements files to newest versions.
  • Update imports to django.urls.reverse so they are compatible with Django 2.0 and 1.8.
  • Make sure that manage.py check exit status is not ignored for setup.py code_quality.
  • Conform to new sorting restrictions for isort.
django-ca -

Published by mathiasertl over 7 years ago

  • Fix signing of wildcard certificates (thanks RedNixon).
  • Add new management commands import_ca and import_cert so users can import existing CAs and certificates (#23).
django-ca - 1.6.0

Published by mathiasertl over 7 years ago

New features and improvements

  • Support CSRs in DER format when signing a certificate via manage.py sign_cert.
  • Support encrypting private keys of CAs with a password.
  • Support Django 1.11.
  • Allow creating CRLs of disabled CAs via manage.py dump_crl.
  • Validate DNSNames when parsing general names. This means that signing a certificate with CommonName that is not a valid domain name fails if it should also be added as subjectAltName (see --cn-in-san option).
  • When configuring django_ca.views.OCSPView, the responder key and certificate are verified during configuration. An erroneous configuration thus throws an error on startup, not during runtime.
  • The testsuite now tests certificate signatures itself via pyOpenSSL, so an independent library is used for verification.

Bugfixes

  • Fix the authorityKeyIdentifier extension when signing certificates with an intermediate CA.
  • Fix creation of intermediate CAs.
django-ca - 1.5.1

Published by mathiasertl over 7 years ago

  • Increase minimum field length of serial and common name fields.
  • Tests now call full_clean() for created models. SQLite (which is used for testing) does not enforce the
    max_length parameter.
django-ca -

Published by mathiasertl over 7 years ago

  • Completely remove pyOpenSSL and consistently use cryptography.
  • Due to the transitition to cryptography, some features have been removed:
    • The tlsfeature extension is no longer supported. It will be again once cryptography adds support.
    • The msCodeInd, msCodeCom, msCTLSign, msEFS values for the ExtendedKeyUsage extension are
      no longer supported. Support for these was largely academic anyway, so they most likely will not be added
      again.
    • TEXT is no longer a supported output format for dumping certificates.
  • The keyUsage extension is now marked as critical for certificate authorities.
  • Add the privilegeWithdrawn and aACompromise attributes for revocation lists.
django-ca - 1.4.1

Published by mathiasertl over 7 years ago

  • Update requirements.
  • Use Travis CI for continuous integration. django-ca is now tested
    with Python 2.7, 3.4, 3.5, 3.6 and nightly, using Django 1.8, 1.9 and 1.10.
  • Fix a few test errors for Django 1.8.
  • Examples now consistently use 4096 bit certificates.
  • Some functionality is now migrated to cryptography in the ongoing process to deprecate
    pyOpenSSL (which is no longer maintained).
  • OCSPView now supports directly passing the public key as bytes. As a consequence, a bad
    certificate is now only detected at runtime.
django-ca - 1.4.0

Published by mathiasertl about 8 years ago

  • Make sure that Child CAs never expire after their parents. If the user specifies an expiry after that of the parent, it is silently changed to the parents expiry.
  • Make sure that certificates never expire after their CAs. If the user specifies an expiry after that of the parent, throw an error.
  • Rename the --days parameter of the sign_cert command to --expires to match what we use for init_ca.
  • Improve help-output of --init-ca and --sign-cert by further grouping arguments into argument groups.
  • Add ability to add CRL-, OCSP- and Issuer-URLs when creating CAs using the --ca-* options.
  • Add support for the nameConstraints X509 extension when creating CAs. The option to the init_ca command is --name-constraint and can be given multiple times to indicate multiple constraints.
  • Add support for the tlsfeature extension, a.k.a. "TLS Must Staple". Since OpenSSL 1.1 is required for this extension, support is currently totally untested.
django-ca - 1.3.0

Published by mathiasertl about 8 years ago

  • Add links for downloading the certificate in PEM/ASN format in the admin interface.
  • Add an extra chapter in documentation on how to create intermediate CAs.
  • Correctly set the issuer field when generating intermediate CAs.
  • fab init_demo now actually creates an intermediate CA.
  • Fix help text for the --parent parameter for``manage.py init_ca`
django-ca - 1.2.0

Published by mathiasertl about 8 years ago

  • django-ca now provides a complete OCSP responder.
  • Various tests are now run with a pre-computed CA, making tests much faster and output more predictable.
  • Update lots of documentation.
django-ca -

Published by mathiasertl over 8 years ago

  • The subject given in the manage.py init_ca and manage.py sign_cert is now given in the
    same form that is frequently used by OpenSSL, "/C=AT/L=...".
  • On the command line, both CAs and certificates can now be named either by their CommonName or
    with their serial. The serial can be given with only the first few letters as long as it's
    unique, as it is matched as long as the serial starts with the given serial.
  • Expiry time of CRLs can now be specified in seconds. manage.py dump_crl now uses the
    --expires instead of the old --days parameter.
  • The admin interface now accounts for cases where some or all CAs are not useable because the
    private key is not accessable. Such a scenario might occur if the private keys are hosted on a
    different machine.
  • The app now provides a generic view to generate CRLs. See Use generic view to host a CRL for more information.
  • Fix the display of the default value of the --ca args.
  • Move this ChangeLog from a top-level .md file here.
  • Fix shell example when issueing certificates.
Package Rankings
Top 6.82% on Pypi.org