-
Notifications
You must be signed in to change notification settings - Fork 39
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
aws-encryption-sdk-python v3.1.1 breaks aws-encryption-cli #307
Comments
Howdy @mpalmer, I attempted to recreate your issue on a Mac Laptop.
Trying this on a Debian EC2 Instance:
Both trials succeeded. In both cases, On Debian, I used Python 3.9.2. So I cannot immediately re-create your issue. Can you tell me what version of Cryptography you are using? Can you tell me what version of Python3.9 you are using? From your stack-trace, I see that you are using the system wide Python. It could be that other packages on your host are requiring a different version This issue is pending a reply from @mpalmer answering the above questions. Much Obliged, |
How odd. Here's the full dpkg and pip package lists:
Running in a venv does seem to work, and the package list is... interestingly different:
That is a very different version of the
So, the problem appears to be that a change that went into |
This PR is in response to [aws/aws-encryption-sdk/issues/307](aws/aws-encryption-sdk-cli#307). It appears that Pyca's Cryptography-3.3.2 does not work in Python3.9 with our library. We need to dive deep on this, and determine which releases of Pyca's Cryptography do work with the latest ESDK-Python.
Problem:
Simple command, taken straight from the fine manual:
When run with
aws-encryption-sdk
v3.1.0, this command succeeds. When run withaws-encryption-sdk
v3.1.1 (ie after runningpip install aws-encryption-sdk==3.1.1
), I get this output and a failure exit status:Chucking in ALL THE VERBOSE (
-vvvv
) I get this:Running an up-to-date Debian 11 ("Bullseye") system in an EC2 instance, built from the official Debian AMI. Nothing particularly fancy in the machine that I can think of -- no fancy env vars, customised config, etc.
The text was updated successfully, but these errors were encountered: