Skip to content

Tracking changes required for full crypto backend independence #114

@mattsb42-aws

Description

@mattsb42-aws

As discussed in #108 and #109, the various cryptographic backends are not all independently operable. This tracking issue will enumerate the changes that need to be made and track the PRs that fix them.

Tags will use the names for dependency grouping as defined in the extras installs, with "base" used to define the python-rsa/python-ecdsa backend.

Known Issues

Test failures

cryptography

base

pycrypto

passing

pycryptodome

passing

compatibility (all backends installed concurrently)

Cross-dependencies

cryptography

CryptographyECKey depends on ecdsa.utils encoding functions.

pycrypto/dome

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions