X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Ffeatures.rst;h=c83b64c22da7539583eceb1f38db13db6a8ebc46;hb=5e98515aa98abf6ad1f650078551e6543d431b99;hp=19cf7f97fa6ebd300c55b1f30ddc22ef28be3e7e;hpb=9c7c8907058265e037945fd96c77aeceb4902623;p=pyderasn.git
diff --git a/doc/features.rst b/doc/features.rst
index 19cf7f9..c83b64c 100644
--- a/doc/features.rst
+++ b/doc/features.rst
@@ -1,3 +1,5 @@
+.. _features:
+
Features
========
@@ -14,33 +16,50 @@ Features
Why yet another library? `pyasn1 `__
had all of this a long time ago. PyDERASN resembles it in many ways. In
practice it should be relatively easy to convert ``pyasn1``'s code to
-``pyderasn``'s one. But additionally it offers:
+``pyderasn``'s one.
+Also there is `asn1crypto `__.
* Small, simple and trying to be reviewable code. Just a single file
-* Automatic decoding of :ref:`DEFINED BY ` fields
+ with `six `__ dependency
* Ability to know :ref:`exact decoded ` objects offsets and
lengths inside the binary
-* :ref:`Pretty printer ` and command-line decoder, that could
- conveniently replace utilities like either ``dumpasn1`` or
- ``openssl asn1parse``
+* Automatic decoding of :ref:`DEFINED BY ` fields
+* Ability to know exact decoded field presence, emptiness: for example
+ ``SEQUENCE`` can lack ``OPTIONAL SEQUENCE OF`` field, but also can
+ have it with no elements inside
+* **Strict** DER-encoding checks. If whole input binary is parsed, then
+ it must be completely valid DER-encoded structure
+* Ability to allow BER-encoded data with knowing if any of specified
+ field has either DER or BER encoding (or possibly indefinite-length
+ encoding). For example
+ `CMS `__
+ structures allow BER encoding for the whole message, except for
+ ``SignedAttributes`` -- you can easily verify your CMS satisfies that
+ requirement
+* Extensive and comprehensive
+ `hypothesis `__
+ driven tests coverage. It also has been fuzzed with
+ `python-afl `__
* Some kind of strong typing: SEQUENCEs require the exact **type** of
- settable values, even when they are inherited
-* However they do not require tags matching: IMPLICIT/EXPLICIT tags will
- be set automatically in the given sequence
+ settable values, even when they are inherited (assigning ``Integer``
+ to the field with the type ``CMSVersion(Integer)`` is not allowed)
+* However they do not require exact tags matching: IMPLICIT/EXPLICIT
+ tags will be set automatically in the given sequence (assigning of
+ ``CMSVersion()`` object to the field ``CMSVersion(expl=...)`` will
+ automatically set required tags)
* Descriptive errors, like ``pyderasn.DecodeError: UTCTime
(tbsCertificate:validity:notAfter:utcTime) (at 328) invalid UTCTime format``
-* ``__slots__`` friendliness
-* Could be significantly faster. For example parsing of CACert.org's CRL
- under Python 3.5.2:
-
- :``python -m pyderasn revoke.crl``:
- ~2 min (``pyderasn == 1.0``)
- :``python -m pyderasn --schema path.to.CertificateList revoke.crl``:
- ~38 sec (``pyderasn == 1.0``)
- :``pyasn1.decode(asn1Spec=pyasn1.CertificateList())``:
- ~22 min (``pyasn1 == 0.2.3``)
+* ``__slots__``, ``copy.copy()`` friendliness
+* Workability with ``pickle``
+* `Cython `__ compatibility
+* Could be significantly :ref:`faster ` and have lower memory usage
+* :ref:`Pretty printer ` and
+ :ref:`command-line decoder `, that could
+ conveniently replace utilities like either ``dumpasn1`` or
+ ``openssl asn1parse``
-There are drawbacks:
+ .. figure:: pprinting.png
+ :alt: Pretty printing example output
-* No old Python versions support
-* See :ref:`limitations `
+ An example of pretty printed X.509 certificate with automatically
+ parsed DEFINED BY fields.