CryptoParser 0.9.1__tar.gz

CryptoParser-0.9.1/CHANGELOG.rst

@@ -0,0 +1,304 @@
+Changelog
+=========
+
+0.9.1 - 2022-06-22
+------------------
+
+-  TLS (``tls``)
+
+   -  Generic
+
+      -  add parser for `signed certificate timestamp <https://www.rfc-editor.org/rfc/rfc6962.html#section-3.3.1>`__
+         entries (#52)
+
+0.9.0 - 2023-04-29
+------------------
+
+-  TLS (``tls``)
+
+   -  Generic
+
+      -  protocol item classes for `OpenVPN <https://en.wikipedia.org/wiki/OpenVPN>`__ support (#62)
+
+0.8.5 - 2023-04-02
+------------------
+
+   -  Generic
+
+      -  move data classes to `CryptoDataHub repository <https://gitlab.com/coroner/cryptodatahub>`__ (#67)
+
+0.8.4 - 2023-01-22
+------------------
+
+-  TLS (``tls``)
+
+   -  Generic
+
+      -  protocol item classes for MySQL support (#61)
+
+0.8.2 - 2022-10-10
+------------------
+
+-  TLS (``tls``)
+
+   -  Cipher Suites (``ciphers``)
+
+      -  add OpenSSL names (#54)
+      -  add min/max versions (#55)
+
+-  SSH (``ssh``)
+
+   -  Public Keys (``pubkeys``)
+
+      -  `HASSH fingerprint <https://engineering.salesforce.com/open-sourcing-hassh-abed3ae5044c/>`__ calculation (#48)
+      -  add `host certificate <https://github.com/openssh/openssh-portable/blob/master/PROTOCOL.certkeys>`__ related
+         classes (#53)
+
+0.8.0 - 2022-01-18
+------------------
+
+-  SSH (``ssh``)
+
+   -  Public Keys (``pubkeys``)
+
+      -  add `public key <https://datatracker.ietf.org/doc/html/rfc4253#section-6.6>`__ related classes (#43)
+
+   -  Versions (``versions``)
+
+      -  add `software version <https://tools.ietf.org/html/rfc4253#section-4.2>`__ related classes (#46)
+
+0.7.3 - 2021-12-26
+------------------
+
+-  Generic
+
+   -  Fix time zone handlind in datetime parser
+
+0.7.2 - 2021-10-07
+------------------
+
+Other
+~~~~~
+
+-  switch to Markdown format in changelog, readme and contributing
+-  update contributing to the latest version from contribution-guide.org
+
+0.7.1 - 2021-09-20
+------------------
+
+-  TLS (``tls``)
+
+   -  protocol item classes for PostgreSQL support (#44)
+
+0.7.0 - 2021-09-02
+------------------
+
+-  TLS (``tls``)
+
+   -  Extensions (``extensions``)
+
+      -  add `application-layer protocol negotiation <https://www.rfc-editor.org/rfc/rfc5077.html>`__ extension related
+         messages (#40)
+      -  add `encrypt-then-MAC <https://www.rfc-editor.org/rfc/rfc7366.html>`__ extension related messages (#40)
+      -  add `extended master secret <https://www.rfc-editor.org/rfc/rfc7627.html>`__ extension related messages (#40)
+      -  add `next protocol negotiation <https://tools.ietf.org/id/draft-agl-tls-nextprotoneg-03.html>`__ extension
+         related messages (#40)
+      -  add `renegotiation indication <https://www.rfc-editor.org/rfc/rfc5746.html>`__ extension related messages (#40)
+      -  add `session ticket <https://www.rfc-editor.org/rfc/rfc5077.html>`__ extension related messages (#40)
+
+0.6.0 - 2021-05-27
+------------------
+
+Features
+~~~~~~~~
+
+-  HTTP(S) (``http``)
+
+   -  Headers (``headers``)
+
+      -  supports header wire format parsing
+      -  add parsers for generic headers
+         (`Content-Type <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type>`__,
+         `Server <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Server>`__)
+      -  add parsers for cache related headers (`Age <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Age>`__,
+         `Cache-Control <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control>`__,
+         `Date <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Date>`__,
+         `ETag <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ETag>`__,
+         `Expires <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires>`__,
+         `Last-Modified <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified>`__,
+         `Pragma <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Pragma>`__)
+      -  add parsers for security related headers
+         (`Expect-CT <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expect-CT>`__,
+         `Expect-Staple <https://scotthelme.co.uk/designing-a-new-security-header-expect-staple>`__,
+         `Referrer-Policy <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy>`__,
+         `Strict-Transport-Security <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security>`__,
+         `X-Content-Type-Options <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options>`__,
+         `X-Frame-Options <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options>`__)
+
+-  TLS (``tls``)
+
+   -  Versions (``versions``)
+
+      -  add `protocol version 1.3 <https://tools.ietf.org/html/rfc8446>`__ related messages (#20)
+
+   -  Cipher Suites (``ciphers``)
+
+      -  add `cipher suites <https://tools.ietf.org/html/rfc8446#appendix-B.4>`__ relate to version 1.3 (#20)
+
+   -  Diffie-Hellman (``dhparams``)
+
+      -  add `supported groups <https://tools.ietf.org/html/rfc8446#section-4.2.7>`__ relate to version 1.3 (#20)
+
+   -  Elliptic Curves (``curves``)
+
+      -  add `supported groups <https://tools.ietf.org/html/rfc8446#section-4.2.7>`__ relate to version 1.3 (#20)
+
+   -  Signature Algorithms (``sigalgos``)
+
+      -  add `signature algorithms <https://tools.ietf.org/html/rfc8446#section-4.2.3>`__ relate to version 1.3 (#20)
+
+0.5.0 - 2021-04-08
+------------------
+
+Features
+~~~~~~~~
+
+-  Generic
+
+   -  add parser for `text-based protocols <https://en.wikipedia.org/wiki/Text-based_protocol>`__ (#21)
+
+-  SSH (``ssh``)
+
+   -  Versions (``versions``)
+
+      -  add `protocol version exchange <https://tools.ietf.org/html/rfc4253#section-4.2>`__ related messages (#21)
+
+-  SSH 2.0 (``ssh2``)
+
+   -  Cipher Suites (``ciphers``)
+
+      -  add `algorithm negotiation <https://tools.ietf.org/html/rfc4253#section-7.1>`__ related messages (#21)
+
+Usability
+~~~~~~~~~
+
+-  Generic
+
+   -  show attributes in user-friendly order in Markdown output (#30)
+   -  use human readable algorithms names in Markdown output (#32)
+   -  add human readable descriptions for exceptions (#33)
+
+0.4.0 - 2021-01-30
+------------------
+
+Features
+~~~~~~~~
+
+-  TLS (``tls``)
+
+   -  Generic
+
+      -  add `LDAP <https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol>`__ related messages (#23)
+
+   -  Client Public Key Request (``pubkeyreq``)
+
+      -  add `client public key request <https://tools.ietf.org/html/rfc2246#section-7.4.4>`__ related messages (#24)
+
+Improvements
+~~~~~~~~~~~~
+
+-  Generic
+
+   -  add `OID <https://en.wikipedia.org/wiki/Object_identifier>`__ to algorithms
+
+0.3.1 - 2020-09-15
+------------------
+
+Features
+~~~~~~~~
+
+-  Generic
+
+   -  `Markdown <https://en.wikipedia.org/wiki/Markdown>`__ serializable format (#19)
+
+Improvements
+~~~~~~~~~~~~
+
+-  TLS (``tls``)
+
+   -  Cipher Suites (``ciphers``)
+
+      -  add missing ``ECDHE_PSK`` cipher suites (#7)
+      -  add `GOST <https://en.wikipedia.org/wiki/GOST>`__ cipher suites
+      -  add missing draft ECC cipher suites (#9)
+      -  add missing `FIPS <https://en.wikipedia.org/wiki/FIPS_140-2>`__ cipher suites (#11)
+      -  add `CECPQ1 <https://en.wikipedia.org/wiki/CECPQ1>`__ cipher suites (#12)
+      -  add missing `Fortezza <https://en.wikipedia.org/wiki/Fortezza>`__ cipher suites (#13)
+      -  add missing ``DHE`` cipher suites (#14)
+      -  add missing SSLv3 cipher suites (#15)
+
+Notable fixes
+~~~~~~~~~~~~~
+
+-  Generic
+
+   -  fix unicode string representation in JSON output (#18)
+
+-  TLS (``tls``)
+
+   -  Cipher Suites (``ciphers``)
+
+      -  fix some cipher suite names and parameters (#7, #10)
+
+0.3.0 - 2020-04-30
+------------------
+
+Features
+~~~~~~~~
+
+-  TLS (``tls``)
+
+   -  protocol item classes for RDP support (#4)
+   -  `JA3 fingerprint <https://engineering.salesforce.com/tls-fingerprinting-with-ja3-and-ja3s-247362855967>`__
+      calculation for TLS client hello (#2)
+
+Bugs
+^^^^
+
+-  TLS (``tls``)
+
+   -  compose all the messages in case of a TLS record (#1)
+
+Refactor
+~~~~~~~~
+
+-  use attrs to avoid boilerplates (#3)
+
+0.2.0 - 2019-12-02
+------------------
+
+Notable fixes
+~~~~~~~~~~~~~
+
+-  clarify TLS related parameter names
+-  several packaging fixes
+
+0.1.0 - 2019-03-20
+------------------
+
+Features
+~~~~~~~~
+
+-  added TLS record protocol support
+-  added TLS ChangeCipherSpec message support
+-  added TLS ApplicationData message support
+-  added TLS handshake message support
+-  added TLS client
+-  added SSL support
+
+Improvements
+~~~~~~~~~~~~
+
+-  added serialization support for classes
+-  added elliptic-curve related descriptive classes
+-  added timeout parameter to TLS client class

CryptoParser-0.9.1/CONTRIBUTING.rst

@@ -0,0 +1,164 @@
+Contributing
+============
+
+Submitting bugs
+---------------
+
+Due diligence
+~~~~~~~~~~~~~
+
+Before submitting a bug, please do the following:
+
+-  Perform **basic troubleshooting** steps:
+
+   -  **Make sure you're on the latest version.** If you're not on the most recent version, your problem may have been
+      solved already! Upgrading is always the best first step.
+   -  **Try older versions.** If you're already *on* the latest release, try rolling back a few minor versions (e.g. if
+      on 1.7, try 1.5 or 1.6) and see if the problem goes away. This will help the devs narrow down when the problem
+      first arose in the commit log.
+   -  **Try switching up dependency versions.** If the software in question has dependencies (other libraries, etc) try
+      upgrading/downgrading those as well.
+
+-  **Search the project's bug/issue tracker** to make sure it's not a known issue.
+-  If you don't find a pre-existing issue, consider **checking with the mailing list and/or IRC channel** in case the
+   problem is non-bug-related.
+
+What to put in your bug report
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Make sure your report gets the attention it deserves: bug reports with missing information may be ignored or punted back
+to you, delaying a fix. The below constitutes a bare minimum; more info is almost always better:
+
+-  **What version of the core programming language interpreter/compiler are you using?** For example, if it's a Python
+   project, are you using Python 2.7.3? Python 3.3.1? PyPy 2.0?
+-  **What operating system are you on?** Windows? (Vista? 7? 32-bit? 64-bit?) Mac OS X? (10.7.4? 10.9.0?) Linux? (Which
+   distro? Which version of that distro? 32 or 64 bits?) Again, more detail is better.
+-  **Which version or versions of the software are you using?** Ideally, you followed the advice above and have ruled
+   out (or verified that the problem exists in) a few different versions.
+-  **How can the developers recreate the bug on their end?** If possible, include a copy of your code, the command you
+   used to invoke it, and the full output of your run (if applicable.)
+
+   -  A common tactic is to pare down your code until a simple (but still bug-causing) "base case" remains. Not only can
+      this help you identify problems which aren't real bugs, but it means the developer can get to fixing the bug
+      faster.
+
+Contributing changes
+--------------------
+
+Licensing of contributed material
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Keep in mind as you contribute, that code, docs and other material submitted to open source projects are usually
+considered licensed under the same terms as the rest of the work.
+
+The details vary from project to project, but from the perspective of this document's authors:
+
+-  Anything submitted to a project falls under the licensing terms in the repository's top level ``LICENSE`` file.
+
+   -  For example, if a project's ``LICENSE`` is BSD-based, contributors should be comfortable with their work
+      potentially being distributed in binary form without the original source code.
+
+-  Per-file copyright/license headers are typically extraneous and undesirable. Please don't add your own copyright
+   headers to new files unless the project's license actually requires them!
+
+   -  Not least because even a new file created by one individual (who often feels compelled to put their personal
+      copyright notice at the top) will inherently end up contributed to by dozens of others over time, making a
+      per-file header outdated/misleading.
+
+Version control branching
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+-  Always **make a new branch** for your work, no matter how small. This makes it easy for others to take just that one
+   set of changes from your repository, in case you have multiple unrelated changes floating around.
+
+   -  A corollary: **don't submit unrelated changes in the same branch/pull request**! The maintainer shouldn't have to
+      reject your awesome bugfix because the feature you put in with it needs more review.
+
+-  **Base your new branch off of the appropriate branch** on the main repository:
+
+   -  **Bug fixes** should be based on the branch named after the **oldest supported release line** the bug affects.
+
+      -  E.g. if a feature was introduced in 1.1, the latest release line is 1.3, and a bug is found in that feature -
+         make your branch based on 1.1. The maintainer will then forward-port it to 1.3 and master.
+      -  Bug fixes requiring large changes to the code or which have a chance of being otherwise disruptive, may need to
+         base off of **master** instead. This is a judgement call -- ask the devs!
+
+   -  **New features** should branch off of **the 'master' branch**.
+
+      -  Note that depending on how long it takes for the dev team to merge your patch, the copy of ``master`` you
+         worked off of may get out of date! If you find yourself 'bumping' a pull request that's been sidelined for a
+         while, **make sure you rebase or merge to latest master** to ensure a speedier resolution.
+
+Code formatting
+~~~~~~~~~~~~~~~
+
+-  **Follow the style you see used in the primary repository**! Consistency with the rest of the project always trumps
+   other considerations. It doesn't matter if you have your own style or if the rest of the code breaks with the greater
+   community - just follow along.
+-  Python projects usually follow the `PEP-8 <http://www.python.org/dev/peps/pep-0008/>`__ guidelines (though many have
+   minor deviations depending on the lead maintainers' preferences.)
+
+Documentation isn't optional
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+It's not! Patches without documentation will be returned to sender. By "documentation" we mean:
+
+-  **Docstrings** (for Python; or API-doc-friendly comments for other languages) must be created or updated for public
+   API functions/methods/etc. (This step is optional for some bugfixes.)
+
+   -  Don't forget to include
+      `versionadded <http://sphinx-doc.org/markup/para.html#directive-versionadded>`__/`versionchanged <http://sphinx-doc.org/markup/para.html#directive-versionchanged>`__
+      ReST directives at the bottom of any new or changed Python docstrings!
+
+      -  Use ``versionadded`` for truly new API members -- new methods, functions, classes or modules.
+      -  Use ``versionchanged`` when adding/removing new function/method arguments, or whenever behavior changes.
+
+-  New features should ideally include updates to **prose documentation**, including useful example code snippets.
+
+-  All submissions should have a **changelog entry** crediting the contributor and/or any individuals instrumental in
+   identifying the problem.
+
+Tests aren't optional
+~~~~~~~~~~~~~~~~~~~~~
+
+Any bugfix that doesn't include a test proving the existence of the bug being fixed, may be suspect. Ditto for new
+features that can't prove they actually work.
+
+We've found that test-first development really helps make features better architected and identifies potential edge
+cases earlier instead of later. Writing tests before the implementation is strongly encouraged.
+
+Full example
+~~~~~~~~~~~~
+
+Here's an example workflow for a project ``theproject`` hosted on Github, which is currently in version 1.3.x. Your
+username is ``yourname`` and you're submitting a basic bugfix. (This workflow only changes slightly if the project is
+hosted at Bitbucket, self-hosted, or etc.)
+
+Preparing your Fork
+^^^^^^^^^^^^^^^^^^^
+
+1. Click 'Fork' on Github, creating e.g. ``yourname/theproject``.
+2. Clone your project: ``git clone git@github.com:yourname/theproject``.
+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 -r dev-requirements.txt``.
+6. Create a branch: ``git checkout -b foo-the-bars 1.3``.
+
+Making your Changes
+^^^^^^^^^^^^^^^^^^^
+
+1. Add changelog entry crediting yourself.
+2. Write tests expecting the correct/fixed functionality; make sure they fail.
+3. Hack, hack, hack.
+4. Run tests again, making sure they pass.
+5. Commit your changes: ``git commit -m "Foo the bars"``
+
+Creating Pull Requests
+^^^^^^^^^^^^^^^^^^^^^^
+
+1. Push your commit to get it back up to your fork: ``git push origin HEAD``
+2. Visit Github, click handy "Pull request" button that it will make upon noticing your new branch.
+3. In the description field, write down issue number (if submitting code fixing an existing issue) or describe the issue
+   + your fix (if submitting a wholly new bugfix).
+4. Hit 'submit'! And please be patient - the maintainers will get to you when they can.

CryptoParser-0.9.1/CryptoParser.egg-info/PKG-INFO

@@ -0,0 +1,96 @@
+Metadata-Version: 2.1
+Name: CryptoParser
+Version: 0.9.1
+Summary: Fast and flexible security protocol parser and generator
+Author: Szilárd Pfeiffer
+Author-email: coroner@pfeifferszilard.hu
+Maintainer: Szilárd Pfeiffer
+Maintainer-email: 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
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Framework :: tox
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Intended Audience :: Science/Research
+Classifier: Intended Audience :: System Administrators
+Classifier: License :: OSI Approved :: Mozilla Public License 2.0 (MPL 2.0)
+Classifier: Natural Language :: English
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 2.7
+Classifier: Programming Language :: Python :: 3.3
+Classifier: Programming Language :: Python :: 3.4
+Classifier: Programming Language :: Python :: 3.5
+Classifier: Programming Language :: Python :: 3.6
+Classifier: Programming Language :: Python :: 3.7
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+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
+Description-Content-Type: text/x-rst
+Provides-Extra: test
+Provides-Extra: pep8
+Provides-Extra: pylint
+License-File: LICENSE.txt
+
+**CryptoParser** is a cryptographic protocol (TLS, SSH) and security-related protocol piece (HTTP headers) parser. It
+is neither a comprehensive nor a secure implementation of any cryptographic protocol. The goal is to support
+testing cryptographic libraries or analysing cryptography-realted settings of application servers such as
+`CryptoLyzer <https://cryptolyzer.readthedocs.io/>`__ does.
+
+Usage
+-----
+
+Pip
+^^^
+
+.. code:: shell
+
+   pip install cryptoparser
+
+Support
+-------
+
+Python implementation
+^^^^^^^^^^^^^^^^^^^^^
+
+-  CPython (2.7, 3.3+)
+-  PyPy (2.7, 3.5+)
+
+Operating systems
+^^^^^^^^^^^^^^^^^
+
+-  Linux
+-  macOS
+-  Windows
+
+License
+-------
+
+The code is available under the terms of Mozilla Public License Version 2.0 (MPL 2.0).
+
+A non-comprehensive, but straightforward description of MPL 2.0 can be found at
+`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-0.9.1/CryptoParser.egg-info/SOURCES.txt

@@ -0,0 +1,44 @@
+CHANGELOG.rst
+CONTRIBUTING.rst
+LICENSE.txt
+MANIFEST.in
+README.rst
+requirements.txt
+setup.py
+CryptoParser.egg-info/PKG-INFO
+CryptoParser.egg-info/SOURCES.txt
+CryptoParser.egg-info/dependency_links.txt
+CryptoParser.egg-info/requires.txt
+CryptoParser.egg-info/top_level.txt
+cryptoparser/__init__.py
+cryptoparser/__setup__.py
+cryptoparser/common/__init__.py
+cryptoparser/common/base.py
+cryptoparser/common/classes.py
+cryptoparser/common/exception.py
+cryptoparser/common/key.py
+cryptoparser/common/parse.py
+cryptoparser/common/utils.py
+cryptoparser/common/x509.py
+cryptoparser/httpx/__init__.py
+cryptoparser/httpx/header.py
+cryptoparser/httpx/parse.py
+cryptoparser/httpx/version.py
+cryptoparser/ssh/__init__.py
+cryptoparser/ssh/key.py
+cryptoparser/ssh/record.py
+cryptoparser/ssh/subprotocol.py
+cryptoparser/ssh/version.py
+cryptoparser/tls/__init__.py
+cryptoparser/tls/algorithm.py
+cryptoparser/tls/ciphersuite.py
+cryptoparser/tls/extension.py
+cryptoparser/tls/grease.py
+cryptoparser/tls/ldap.py
+cryptoparser/tls/mysql.py
+cryptoparser/tls/openvpn.py
+cryptoparser/tls/postgresql.py
+cryptoparser/tls/rdp.py
+cryptoparser/tls/record.py
+cryptoparser/tls/subprotocol.py
+cryptoparser/tls/version.py

CryptoParser-0.9.1/CryptoParser.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

CryptoParser-0.9.1/CryptoParser.egg-info/requires.txt

@@ -0,0 +1,26 @@
+asn1crypto
+attrs<22.0.1,>=19.1
+cryptodatahub>=0.9.1
+python-dateutil
+python-dateutil
+
+[:python_version < "3.4"]
+py2-ipaddress
+
+[:python_version < "3.5"]
+typing
+
+[:python_version < '3']
+enum34==1.1.6
+pathlib2==2.3.7.post1
+Mock
+unittest2
+
+[pep8]
+flake8
+
+[pylint]
+pylint
+
+[test]
+coverage

CryptoParser-0.9.1/CryptoParser.egg-info/top_level.txt

@@ -0,0 +1 @@
+cryptoparser