Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conda-content-trust is incompatible with cryptography=41.0.0 #56

Closed
kenodegard opened this issue Jun 1, 2023 · 1 comment · Fixed by #57
Closed

conda-content-trust is incompatible with cryptography=41.0.0 #56

kenodegard opened this issue Jun 1, 2023 · 1 comment · Fixed by #57
Assignees
Labels
source::anaconda created by members of Anaconda, Inc. type::bug describes erroneous operation, use severity::* to classify the type

Comments

@kenodegard
Copy link
Contributor

kenodegard commented Jun 1, 2023

What happened?

The recently released cryptography=41.0.0 introduces breaking changes that are incompatible with conda-content-trust.

To reproduce:

CONDA_CHANNELS=conda-forge conda create -n scratch conda-content-trust cryptography=41
conda run -n scratch python -c "from conda_content_trust.common import SignatureError"

This was discovered while running conda's conda-forge test suite: https://github.com/conda/conda/actions/runs/5137836382/jobs/9249611836

@kenodegard kenodegard added type::bug describes erroneous operation, use severity::* to classify the type source::anaconda created by members of Anaconda, Inc. labels Jun 1, 2023
@kenodegard kenodegard changed the title conda-content-trust is incompatible with cryptography=41 conda-content-trust is incompatible with cryptography=41.0.0 Jun 1, 2023
@jezdez
Copy link
Member

jezdez commented Jun 1, 2023

This is related to implementing ed25519 in Rust: pyca/cryptography#8697

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
source::anaconda created by members of Anaconda, Inc. type::bug describes erroneous operation, use severity::* to classify the type
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants