tree: 305f2a3dc8c41477722ea00f7bf81d4993bbd5ef [path history] [tgz]
  1. .gitignore
  2. .travis.yml
  8. appveyor.yml
  9. asn1crypto/
  11. circle.yml
  12. codecov.json
  13. dev/
  14. docs/
  16. requires/
  19. tests/
  20. tox.ini


A fast, pure Python library for parsing and serializing ASN.1 structures.

Travis CI AppVeyor CircleCI Codecov PyPI


In addition to an ASN.1 BER/DER decoder and DER serializer, the project includes a bunch of ASN.1 structures for use with various common cryptography standards:

X.509asn1crypto.x509RFC 5280
CRLasn1crypto.crlRFC 5280
CSRasn1crypto.csrRFC 2986, RFC 2985
OCSPasn1crypto.ocspRFC 6960
PKCS#12asn1crypto.pkcs12RFC 7292
PKCS#8asn1crypto.keysRFC 5208
PKCS#1 v2.1 (RSA keys)asn1crypto.keysRFC 3447
DSA keysasn1crypto.keysRFC 3279
Elliptic curve keysasn1crypto.keysSECG SEC1 V2
PKCS#3 v1.4asn1crypto.algosPKCS#3 v1.4
PKCS#5 v2.1asn1crypto.algosPKCS#5 v2.1
CMS (and PKCS#7)asn1crypto.cmsRFC 5652, RFC 2315
TSPasn1crypto.tspRFC 3161
PDF signaturesasn1crypto.pdfPDF 1.7

Why Another Python ASN.1 Library?

Python has long had the pyasn1 and pyasn1_modules available for parsing and serializing ASN.1 structures. While the project does include a comprehensive set of tools for parsing and serializing, the performance of the library can be very poor, especially when dealing with bit fields and parsing large structures such as CRLs.

After spending extensive time using pyasn1, the following issues were identified:

  1. Poor performance
  2. Verbose, non-pythonic API
  3. Out-dated and incomplete definitions in pyasn1-modules
  4. No simple way to map data to native Python data structures
  5. No mechanism for overridden universal ASN.1 types

The pyasn1 API is largely method driven, and uses extensive configuration objects and lowerCamelCase names. There were no consistent options for converting types of native Python data structures. Since the project supports out-dated versions of Python, many newer language features are unavailable for use.

Time was spent trying to profile issues with the performance, however the architecture made it hard to pin down the primary source of the poor performance. Attempts were made to improve performance by utilizing unreleased patches and delaying parsing using the Any type. Even with such changes, the performance was still unacceptably slow.

Finally, a number of structures in the cryptographic space use universal data types such as BitString and OctetString, but interpret the data as other types. For instance, signatures are really byte strings, but are encoded as BitString. Elliptic curve keys use both BitString and OctetString to represent integers. Parsing these structures as the base universal types and then re-interpreting them wastes computation.

asn1crypto uses the following techniques to improve performance, especially when extracting one or two fields from large, complex structures:

  • Delayed parsing of byte string values
  • Persistence of original ASN.1 encoded data until a value is changed
  • Lazy loading of child fields
  • Utilization of high-level Python stdlib modules

While there is no extensive performance test suite, the CRLTests.test_parse_crl test case was used to parse a 21MB CRL file on a late 2013 rMBP. asn1crypto parsed the certificate serial numbers in just under 8 seconds. With pyasn1, using definitions from pyasn1-modules, the same parsing took over 4,100 seconds.

For smaller structures the performance difference can range from a few times faster to an order of magnitude of more.

Related Crypto Libraries

asn1crypto is part of the modularcrypto family of Python packages:

Current Release

0.24.0 - changelog


Python 2.6, 2.7, 3.2, 3.3, 3.4, 3.5, 3.6 or pypy. No third-party packages required.


pip install asn1crypto


asn1crypto is licensed under the terms of the MIT license. See the LICENSE file for the exact license text.


The documentation for asn1crypto is composed of tutorials on basic usage and links to the source for the various pre-defined type classes.



Continuous Integration


Tests are written using unittest and require no third-party packages:

python tests

To run only some tests, pass a regular expression as a parameter to tests.

python tests ocsp


To install the package used for linting, execute:

pip install --user -r requires/lint

The following command will run the linter:

python lint

Support for code coverage can be installed via:

pip install --user -r requires/coverage

Coverage is measured by running:

python coverage

To install the necessary packages for releasing a new version on PyPI, run:

pip install --user -r requires/release

Releases are created by:

  • Making a git tag in semver format

  • Running the command:

    python release

Existing releases can be found at

CI Tasks

A task named deps exists to ensure a modern version of pip is installed, along with all necessary testing dependencies.

The ci task runs lint (if flake8 is available for the version of Python) and coverage (or tests if coverage is not available for the version of Python). If the current directory is a clean git working copy, the coverage data is submitted to

python deps
python ci