cryptoparser 1.4.0__tar.gz → 1.6.0__tar.gz

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/.gitignore

@@ -14,3 +14,4 @@
 /Pipfile.lock
 /build
 /dist
+/uv.lock

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/.gitlab-ci.yml

@@ -7,24 +7,25 @@ stages:
 
 before_script:
 - pip install uv
-- uv pip install --system .[tests]
+- uv sync --extra tests
 
 variables:
   GIT_SUBMODULE_DEPTH: 1
   GIT_SUBMODULE_STRATEGY: recursive
   PYTHONPATH: "submodules/cryptodatahub"
+  UV_PYTHON_DOWNLOADS: "never"
+  UV_PYTHON_PREFERENCE: "only-system"
 
 .test:
   script:
-  - coverage run -m unittest discover -v
-  - coverage report
+  - uv run coverage run -m unittest discover -v
+  - uv run coverage report
 
 pylint:
   image: python:3.14-slim
   stage: earlytest
   script:
-  - uv pip install --system pylint
-  - pylint --rcfile .pylintrc cryptoparser docs test
+  - uv run --with pylint pylint --rcfile .pylintrc cryptoparser docs test
 
 ruff:
   image: python:3.14-slim
@@ -83,9 +84,8 @@ coveralls:
     PYTHONPATH: "submodules/cryptodatahub"
   stage: deploy
   script:
-    - uv pip install --system coveralls
-    - coverage run -m unittest -v -f
-    - coveralls
+    - uv run coverage run -m unittest -v -f
+    - uv run --with coveralls coveralls
   only:
     refs:
       - master

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/.pylintrc

@@ -6,6 +6,10 @@ jobs=0
 
 load-plugins = pylint.extensions.no_self_use
 
+[BASIC]
+
+good-names=setUp,tearDown,setUpClass,tearDownClass
+
 [FORMAT]
 
 max-line-length=120

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/CHANGELOG.rst

@@ -2,6 +2,84 @@
 Changelog
 =========
 
+------------------
+1.6.0 - 2026-08-25
+------------------
+
+Features
+========
+
+-  TLS (``tls``)
+
+   -  Extensions (``extensions``)
+
+      -  add `trust anchors <https://datatracker.ietf.org/doc/draft-ietf-tls-trust-anchor-ids/>`__ extension related
+         messages (#104)
+      -  add server padding extension related messages (#104)
+      -  add `application-layer protocol settings <https://datatracker.ietf.org/doc/draft-vvv-tls-alps/>`__ extension
+         related messages with the old code point (#104)
+
+Notable fixes
+=============
+
+-  TLS (``tls``)
+
+   -  Extensions (``extensions``)
+
+      -  bound the outer extension payload of the encrypted client hello by the extension length (#104)
+
+-  IKE (``ike``)
+
+   -  preserve the transform number when parsing the IKEv1 transform payload (#105)
+
+Refactor
+========
+
+-  Generic
+
+   -  follow the replacement of the named group with the key parameter (#106)
+
+-  TLS (``tls``)
+
+   -  make the parameter classes of the invalid extension types immutable (#104)
+
+Other
+=====
+
+-  switch to Markdown format in readme
+-  add llms.txt to describe the library for large language models
+-  use uv instead of pipenv and pip in the documentation
+
+------------------
+1.5.0 - 2026-07-31
+------------------
+
+Features
+========
+
+-  IKE (``ike``)
+
+   -  add IKEv1 and IKEv2 certificate payload parsing (#103)
+   -  add IKEv1 identification payload parsing (#103)
+   -  add IKEv1 signature payload parsing (#103)
+   -  add IKEv2 identification payload parsing (#103)
+   -  add IKEv2 authentication payload parsing (#103)
+   -  add IKEv2 extensible authentication protocol payload parsing (#103)
+   -  add IKEv2 encrypted and authenticated payload parsing (#103)
+   -  keep IKEv1 and IKEv2 payloads of unknown type unparsed instead of rejecting the message (#103)
+   -  add getter for the distinguished name of the IKEv1 certificate request payload (#103)
+   -  add getter for the certification authority hashes of the IKEv2 certificate request payload (#103)
+
+Refactor
+========
+
+-  IKE (``ike``)
+
+   -  parse the IKEv1 and IKEv2 identification payload data according to the identification type (#103)
+   -  parse the digital signature envelope of the IKEv2 authentication payload (#103)
+   -  split the ISAKMP message parsing and composing into header and payload chain steps (#103)
+   -  use typed values in the IKEv2 signature hash algorithms notify payload (#103)
+
 ------------------
 1.4.0 - 2026-07-17
 ------------------

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/CONTRIBUTING.rst

@@ -142,7 +142,7 @@ Preparing your Fork
 3. ``cd theproject``
 4. `Create and activate a virtual
    environment <https://packaging.python.org/tutorials/installing-packages/#creating-virtual-environments>`__.
-5. Install the development requirements: ``pip install .[tests]``.
+5. Install the development requirements: ``uv sync --extra tests``.
 6. Create a branch: ``git checkout -b foo-the-bars 1.3``.
 
 Making your Changes

cryptoparser-1.6.0/CryptoParser.egg-info/PKG-INFO

@@ -0,0 +1,154 @@
+Metadata-Version: 2.4
+Name: CryptoParser
+Version: 1.6.0
+Summary: An analysis oriented security protocol parser and generator
+Author-email: Szilárd Pfeiffer <coroner@pfeifferszilard.hu>
+Maintainer-email: Szilárd Pfeiffer <coroner@pfeifferszilard.hu>
+License: MPL-2.0
+Project-URL: Homepage, https://gitlab.com/coroner/cryptoparser
+Project-URL: Changelog, https://cryptoparser.readthedocs.io/en/latest/changelog
+Project-URL: Documentation, https://cryptoparser.readthedocs.io/en/latest/
+Project-URL: Issues, https://gitlab.com/coroner/cryptoparser/-/issues
+Project-URL: Source, https://gitlab.com/coroner/cryptoparser
+Keywords: ssl,tls,gost,ja3,ldap,rdp,ssh,hsts,dns,ike
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Information Technology
+Classifier: Intended Audience :: Science/Research
+Classifier: Intended Audience :: System Administrators
+Classifier: Natural Language :: English
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Classifier: Programming Language :: Python
+Classifier: Topic :: Internet
+Classifier: Topic :: Security
+Classifier: Topic :: Security :: Cryptography
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Software Development :: Testing :: Traffic Generation
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Requires-Dist: asn1crypto
+Requires-Dist: attrs
+Requires-Dist: cryptodatahub==1.6.0
+Requires-Dist: urllib3
+Provides-Extra: tests
+Requires-Dist: pyfakefs; extra == "tests"
+Requires-Dist: coverage; extra == "tests"
+Provides-Extra: docs
+Requires-Dist: myst-parser; extra == "docs"
+Requires-Dist: sphinx; extra == "docs"
+Requires-Dist: sphinx-sitemap; extra == "docs"
+Requires-Dist: docutils; extra == "docs"
+Dynamic: license-file
+
+[![Pipeline](https://gitlab.com/coroner/cryptoparser/badges/master/pipeline.svg)](https://gitlab.com/coroner/cryptoparser/-/pipelines/master/latest)
+[![Test Coverage](https://coveralls.io/repos/gitlab/coroner/cryptoparser/badge.svg?branch=master)](https://coveralls.io/gitlab/coroner/cryptoparser/)
+[![Documentation](https://readthedocs.org/projects/cryptoparser/badge/?version=latest)](https://cryptoparser.readthedocs.io)
+
+<!-- documentation-summary-start -->
+**CryptoParser** is a cryptographic protocol
+([IKE](https://en.wikipedia.org/wiki/Internet_Key_Exchange),
+[SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security#SSL_1.0,_2.0,_and_3.0),
+[TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security),
+[SSH](https://en.wikipedia.org/wiki/Secure_Shell),
+[DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions)) and security-related protocol piece
+([HTTP headers](https://en.wikipedia.org/wiki/List_of_HTTP_header_fields)) parser and generator. It is neither a
+comprehensive nor a secure implementation of any cryptographic protocol. The goal is to support testing cryptographic
+libraries or analysing cryptography-related settings of application servers such as
+[CryptoLyzer](https://cryptolyzer.readthedocs.io/) does.
+
+**Use CryptoParser when you need to parse handshake messages** — it implements the wire format of ISAKMP, IKEv1, IKEv2,
+SSL 2.0, SSL 3.0, TLS 1.0 to TLS 1.3, and SSH 2.0, so a message can be read field by field instead of being handed to a
+connection-oriented library.
+
+**Use CryptoParser when you need to generate messages a library refuses to send** — analysis means triggering special
+and corner cases, so messages can be composed with deprecated, experimental, or plainly invalid values that an
+implementation aiming for secure connections would reject.
+
+**Use CryptoParser when you need parsed HTTP security headers** — beyond wire format parsing it parses individual
+headers, so directives are available as typed values rather than as strings.
+
+**Use CryptoParser when you need DNSSEC record parsing** — DNSSEC records are parsed into the same kind of typed
+structures as the protocol messages.
+<!-- documentation-summary-end -->
+
+<!-- documentation-strength-start -->
+The strength of CryptoParser is that it is backed by the most comprehensive algorithm identifier database available
+([CryptoDataHub](https://cryptodatahub.readthedocs.io)). This makes it possible to recognize rarely used, deprecated,
+non-standard, or experimental algorithms that are not supported by any version of OpenSSL, GnuTLS, LibreSSL, or
+wolfSSL.
+<!-- documentation-strength-end -->
+
+## Why CryptoParser?
+
+<!-- documentation-comparison-start -->
+- **Analysis oriented** — the library implements only the parts of a protocol that analysis needs, and deliberately
+  keeps the parts that make a message invalid.
+- **No OpenSSL dependency** — the protocol implementation is its own, so what can be parsed or generated is not limited
+  by what a cryptographic library is willing to do.
+- **Typed values, not byte offsets** — algorithm identifiers, protocol versions, and header directives are parsed into
+  enumerations and attribute classes.
+- **Symmetric parsing and composing** — every parsable piece can also be composed back to its wire format.
+<!-- documentation-comparison-end -->
+
+## Usage
+
+### uv
+
+```shell
+uv add cryptoparser
+```
+
+```python
+from cryptoparser.tls.version import TlsProtocolVersion
+
+# parse a protocol version from its wire format
+TlsProtocolVersion.parse_exact_size(b'\x03\x03')
+# TLS 1.2
+
+# compose a protocol version back to its wire format
+TlsProtocolVersion.parse_exact_size(b'\x03\x04').compose()
+# bytearray(b'\x03\x04')
+```
+
+## Support
+
+**Python implementations**
+
+- CPython 3.9+
+- PyPy 3.9+
+
+**Operating systems**
+
+- Linux
+- macOS
+- Windows
+
+## Documentation
+
+Detailed [documentation](https://cryptoparser.readthedocs.io) is available on the project's
+[Read the Docs](https://readthedocs.com) site.
+
+## License
+
+The [code](https://gitlab.com/coroner/cryptoparser) is available under the terms of
+[Mozilla Public License Version 2.0](https://www.mozilla.org/en-US/MPL/2.0/) (MPL 2.0).
+
+A non-comprehensive but straightforward description of MPL 2.0 can be found at the
+[Choose an open source license](https://choosealicense.com/licenses#mpl-2.0) website.
+
+## Credits
+
+- [NLnet Foundation](https://nlnet.nl) and [NGI Assure](https://www.assure.ngi.eu), supports the project part of the
+  [Next Generation Internet](https://ngi.eu) initiative.

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/CryptoParser.egg-info/SOURCES.txt

@@ -8,8 +8,9 @@ CHANGELOG.rst
 CONTRIBUTING.rst
 LICENSE.txt
 MANIFEST.in
-README.rst
+README.md
 cryptoparser.spec
+llms.txt
 pyproject.toml
 setup.py
 CryptoParser.egg-info/PKG-INFO

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/CryptoParser.egg-info/requires.txt

@@ -1,9 +1,10 @@
 asn1crypto
 attrs
-cryptodatahub==1.4.0
+cryptodatahub==1.6.0
 urllib3
 
 [docs]
+myst-parser
 sphinx
 sphinx-sitemap
 docutils

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/MANIFEST.in

@@ -1,2 +1,3 @@
+include *.md
 include *.rst
 prune submodules

cryptoparser-1.6.0/PKG-INFO

@@ -0,0 +1,154 @@
+Metadata-Version: 2.4
+Name: CryptoParser
+Version: 1.6.0
+Summary: An analysis oriented security protocol parser and generator
+Author-email: Szilárd Pfeiffer <coroner@pfeifferszilard.hu>
+Maintainer-email: Szilárd Pfeiffer <coroner@pfeifferszilard.hu>
+License: MPL-2.0
+Project-URL: Homepage, https://gitlab.com/coroner/cryptoparser
+Project-URL: Changelog, https://cryptoparser.readthedocs.io/en/latest/changelog
+Project-URL: Documentation, https://cryptoparser.readthedocs.io/en/latest/
+Project-URL: Issues, https://gitlab.com/coroner/cryptoparser/-/issues
+Project-URL: Source, https://gitlab.com/coroner/cryptoparser
+Keywords: ssl,tls,gost,ja3,ldap,rdp,ssh,hsts,dns,ike
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Information Technology
+Classifier: Intended Audience :: Science/Research
+Classifier: Intended Audience :: System Administrators
+Classifier: Natural Language :: English
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Classifier: Programming Language :: Python
+Classifier: Topic :: Internet
+Classifier: Topic :: Security
+Classifier: Topic :: Security :: Cryptography
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Software Development :: Testing :: Traffic Generation
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Requires-Dist: asn1crypto
+Requires-Dist: attrs
+Requires-Dist: cryptodatahub==1.6.0
+Requires-Dist: urllib3
+Provides-Extra: tests
+Requires-Dist: pyfakefs; extra == "tests"
+Requires-Dist: coverage; extra == "tests"
+Provides-Extra: docs
+Requires-Dist: myst-parser; extra == "docs"
+Requires-Dist: sphinx; extra == "docs"
+Requires-Dist: sphinx-sitemap; extra == "docs"
+Requires-Dist: docutils; extra == "docs"
+Dynamic: license-file
+
+[![Pipeline](https://gitlab.com/coroner/cryptoparser/badges/master/pipeline.svg)](https://gitlab.com/coroner/cryptoparser/-/pipelines/master/latest)
+[![Test Coverage](https://coveralls.io/repos/gitlab/coroner/cryptoparser/badge.svg?branch=master)](https://coveralls.io/gitlab/coroner/cryptoparser/)
+[![Documentation](https://readthedocs.org/projects/cryptoparser/badge/?version=latest)](https://cryptoparser.readthedocs.io)
+
+<!-- documentation-summary-start -->
+**CryptoParser** is a cryptographic protocol
+([IKE](https://en.wikipedia.org/wiki/Internet_Key_Exchange),
+[SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security#SSL_1.0,_2.0,_and_3.0),
+[TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security),
+[SSH](https://en.wikipedia.org/wiki/Secure_Shell),
+[DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions)) and security-related protocol piece
+([HTTP headers](https://en.wikipedia.org/wiki/List_of_HTTP_header_fields)) parser and generator. It is neither a
+comprehensive nor a secure implementation of any cryptographic protocol. The goal is to support testing cryptographic
+libraries or analysing cryptography-related settings of application servers such as
+[CryptoLyzer](https://cryptolyzer.readthedocs.io/) does.
+
+**Use CryptoParser when you need to parse handshake messages** — it implements the wire format of ISAKMP, IKEv1, IKEv2,
+SSL 2.0, SSL 3.0, TLS 1.0 to TLS 1.3, and SSH 2.0, so a message can be read field by field instead of being handed to a
+connection-oriented library.
+
+**Use CryptoParser when you need to generate messages a library refuses to send** — analysis means triggering special
+and corner cases, so messages can be composed with deprecated, experimental, or plainly invalid values that an
+implementation aiming for secure connections would reject.
+
+**Use CryptoParser when you need parsed HTTP security headers** — beyond wire format parsing it parses individual
+headers, so directives are available as typed values rather than as strings.
+
+**Use CryptoParser when you need DNSSEC record parsing** — DNSSEC records are parsed into the same kind of typed
+structures as the protocol messages.
+<!-- documentation-summary-end -->
+
+<!-- documentation-strength-start -->
+The strength of CryptoParser is that it is backed by the most comprehensive algorithm identifier database available
+([CryptoDataHub](https://cryptodatahub.readthedocs.io)). This makes it possible to recognize rarely used, deprecated,
+non-standard, or experimental algorithms that are not supported by any version of OpenSSL, GnuTLS, LibreSSL, or
+wolfSSL.
+<!-- documentation-strength-end -->
+
+## Why CryptoParser?
+
+<!-- documentation-comparison-start -->
+- **Analysis oriented** — the library implements only the parts of a protocol that analysis needs, and deliberately
+  keeps the parts that make a message invalid.
+- **No OpenSSL dependency** — the protocol implementation is its own, so what can be parsed or generated is not limited
+  by what a cryptographic library is willing to do.
+- **Typed values, not byte offsets** — algorithm identifiers, protocol versions, and header directives are parsed into
+  enumerations and attribute classes.
+- **Symmetric parsing and composing** — every parsable piece can also be composed back to its wire format.
+<!-- documentation-comparison-end -->
+
+## Usage
+
+### uv
+
+```shell
+uv add cryptoparser
+```
+
+```python
+from cryptoparser.tls.version import TlsProtocolVersion
+
+# parse a protocol version from its wire format
+TlsProtocolVersion.parse_exact_size(b'\x03\x03')
+# TLS 1.2
+
+# compose a protocol version back to its wire format
+TlsProtocolVersion.parse_exact_size(b'\x03\x04').compose()
+# bytearray(b'\x03\x04')
+```
+
+## Support
+
+**Python implementations**
+
+- CPython 3.9+
+- PyPy 3.9+
+
+**Operating systems**
+
+- Linux
+- macOS
+- Windows
+
+## Documentation
+
+Detailed [documentation](https://cryptoparser.readthedocs.io) is available on the project's
+[Read the Docs](https://readthedocs.com) site.
+
+## License
+
+The [code](https://gitlab.com/coroner/cryptoparser) is available under the terms of
+[Mozilla Public License Version 2.0](https://www.mozilla.org/en-US/MPL/2.0/) (MPL 2.0).
+
+A non-comprehensive but straightforward description of MPL 2.0 can be found at the
+[Choose an open source license](https://choosealicense.com/licenses#mpl-2.0) website.
+
+## Credits
+
+- [NLnet Foundation](https://nlnet.nl) and [NGI Assure](https://www.assure.ngi.eu), supports the project part of the
+  [Next Generation Internet](https://ngi.eu) initiative.

cryptoparser-1.6.0/README.md

@@ -0,0 +1,100 @@
+[![Pipeline](https://gitlab.com/coroner/cryptoparser/badges/master/pipeline.svg)](https://gitlab.com/coroner/cryptoparser/-/pipelines/master/latest)
+[![Test Coverage](https://coveralls.io/repos/gitlab/coroner/cryptoparser/badge.svg?branch=master)](https://coveralls.io/gitlab/coroner/cryptoparser/)
+[![Documentation](https://readthedocs.org/projects/cryptoparser/badge/?version=latest)](https://cryptoparser.readthedocs.io)
+
+<!-- documentation-summary-start -->
+**CryptoParser** is a cryptographic protocol
+([IKE](https://en.wikipedia.org/wiki/Internet_Key_Exchange),
+[SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security#SSL_1.0,_2.0,_and_3.0),
+[TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security),
+[SSH](https://en.wikipedia.org/wiki/Secure_Shell),
+[DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions)) and security-related protocol piece
+([HTTP headers](https://en.wikipedia.org/wiki/List_of_HTTP_header_fields)) parser and generator. It is neither a
+comprehensive nor a secure implementation of any cryptographic protocol. The goal is to support testing cryptographic
+libraries or analysing cryptography-related settings of application servers such as
+[CryptoLyzer](https://cryptolyzer.readthedocs.io/) does.
+
+**Use CryptoParser when you need to parse handshake messages** — it implements the wire format of ISAKMP, IKEv1, IKEv2,
+SSL 2.0, SSL 3.0, TLS 1.0 to TLS 1.3, and SSH 2.0, so a message can be read field by field instead of being handed to a
+connection-oriented library.
+
+**Use CryptoParser when you need to generate messages a library refuses to send** — analysis means triggering special
+and corner cases, so messages can be composed with deprecated, experimental, or plainly invalid values that an
+implementation aiming for secure connections would reject.
+
+**Use CryptoParser when you need parsed HTTP security headers** — beyond wire format parsing it parses individual
+headers, so directives are available as typed values rather than as strings.
+
+**Use CryptoParser when you need DNSSEC record parsing** — DNSSEC records are parsed into the same kind of typed
+structures as the protocol messages.
+<!-- documentation-summary-end -->
+
+<!-- documentation-strength-start -->
+The strength of CryptoParser is that it is backed by the most comprehensive algorithm identifier database available
+([CryptoDataHub](https://cryptodatahub.readthedocs.io)). This makes it possible to recognize rarely used, deprecated,
+non-standard, or experimental algorithms that are not supported by any version of OpenSSL, GnuTLS, LibreSSL, or
+wolfSSL.
+<!-- documentation-strength-end -->
+
+## Why CryptoParser?
+
+<!-- documentation-comparison-start -->
+- **Analysis oriented** — the library implements only the parts of a protocol that analysis needs, and deliberately
+  keeps the parts that make a message invalid.
+- **No OpenSSL dependency** — the protocol implementation is its own, so what can be parsed or generated is not limited
+  by what a cryptographic library is willing to do.
+- **Typed values, not byte offsets** — algorithm identifiers, protocol versions, and header directives are parsed into
+  enumerations and attribute classes.
+- **Symmetric parsing and composing** — every parsable piece can also be composed back to its wire format.
+<!-- documentation-comparison-end -->
+
+## Usage
+
+### uv
+
+```shell
+uv add cryptoparser
+```
+
+```python
+from cryptoparser.tls.version import TlsProtocolVersion
+
+# parse a protocol version from its wire format
+TlsProtocolVersion.parse_exact_size(b'\x03\x03')
+# TLS 1.2
+
+# compose a protocol version back to its wire format
+TlsProtocolVersion.parse_exact_size(b'\x03\x04').compose()
+# bytearray(b'\x03\x04')
+```
+
+## Support
+
+**Python implementations**
+
+- CPython 3.9+
+- PyPy 3.9+
+
+**Operating systems**
+
+- Linux
+- macOS
+- Windows
+
+## Documentation
+
+Detailed [documentation](https://cryptoparser.readthedocs.io) is available on the project's
+[Read the Docs](https://readthedocs.com) site.
+
+## License
+
+The [code](https://gitlab.com/coroner/cryptoparser) is available under the terms of
+[Mozilla Public License Version 2.0](https://www.mozilla.org/en-US/MPL/2.0/) (MPL 2.0).
+
+A non-comprehensive but straightforward description of MPL 2.0 can be found at the
+[Choose an open source license](https://choosealicense.com/licenses#mpl-2.0) website.
+
+## Credits
+
+- [NLnet Foundation](https://nlnet.nl) and [NGI Assure](https://www.assure.ngi.eu), supports the project part of the
+  [Next Generation Internet](https://ngi.eu) initiative.

{cryptoparser-1.4.0 → cryptoparser-1.6.0}/cryptoparser/dnsrec/record.py

@@ -7,7 +7,8 @@ import enum
 
 import attr
 
-from cryptodatahub.common.algorithm import Authentication, NamedGroup, Signature
+from cryptodatahub.common.algorithm import Authentication, Signature
+from cryptodatahub.common.parameter import ECParamWellKnown
 from cryptodatahub.common.exception import InvalidValue
 from cryptodatahub.common.key import (
     PublicKey,
@@ -68,7 +69,7 @@ class DnsRecordDnskey(ParsableBase, Serializable):
         algorithm_compatible_gost = (
             self.algorithm == DnsSecAlgorithm.ECCGOST and
             self.key.key_type == Authentication.ECDSA and
-            self.key.params.named_group == NamedGroup.GC256B
+            self.key.params.key_parameter == ECParamWellKnown.GC256B
         )
         if (algorithm_incompatible and not algorithm_compatible_gost):
             raise InvalidValue(algorithm_key_type, type(self), 'key_type')
@@ -113,35 +114,35 @@ class DnsRecordDnskey(ParsableBase, Serializable):
     @classmethod
     def _parse_public_key_ecdsa(cls, dnssec_algorithm, key_parser):
         if dnssec_algorithm == DnsSecAlgorithm.ECDSAP256SHA256:
-            named_group = NamedGroup.SECP256K1
+            key_parameter = ECParamWellKnown.SECP256K1
         elif dnssec_algorithm == DnsSecAlgorithm.ECDSAP384SHA384:
-            named_group = NamedGroup.SECP384R1
+            key_parameter = ECParamWellKnown.SECP384R1
         elif dnssec_algorithm == DnsSecAlgorithm.ECCGOST:
-            named_group = NamedGroup.GC256B
+            key_parameter = ECParamWellKnown.GC256B
         else:
             raise NotImplementedError(dnssec_algorithm)
 
-        key_size = named_group.value.size // 8
+        key_size = key_parameter.value.field_size // 8
         key_parser.parse_mpint('x', key_size)
         key_parser.parse_mpint('y', key_size)
 
         return PublicKey.from_params(PublicKeyParamsEcdsa(
-            point_x=key_parser['x'], point_y=key_parser['y'], named_group=named_group,
+            point_x=key_parser['x'], point_y=key_parser['y'], key_parameter=key_parameter,
         ))
 
     @classmethod
     def _parse_public_key_eddsa(cls, dnssec_algorithm, key_parser):
         if dnssec_algorithm == DnsSecAlgorithm.ED25519:
-            curve_type = NamedGroup.CURVE25519
+            key_parameter = ECParamWellKnown.CURVE25519
             key_parser.parse_raw('public_key', 256 // 8)
         elif dnssec_algorithm == DnsSecAlgorithm.ED448:
-            curve_type = NamedGroup.CURVE448
+            key_parameter = ECParamWellKnown.CURVE448
             key_parser.parse_raw('public_key', 448 // 8)
         else:
             raise NotImplementedError(dnssec_algorithm)
 
         return PublicKey.from_params(PublicKeyParamsEddsa(
-            curve_type=curve_type, key_data=key_parser['public_key']
+            key_parameter=key_parameter, key_data=key_parser['public_key']
         ))
 
     @classmethod