texastony
commented
2 years ago Howdy @mpalmer, Thank you for bringing this to our attention.
I attempted to recreate your issue on a Mac Laptop.
mkdir temp; cd temp;
python -m venv venv; source venv/bin/activate;
python -m pip install aws-encryption-sdk-cli==4.1.0;
echo “hello world” > hello.txt;
// action to fetch AWS credentials
keyArn=$AWS_ENCRYPTION_SDK_PYTHON_INTEGRATION_TEST_AWS_KMS_KEY_ID;
aws-encryption-cli --encrypt \
--input hello.txt \
--wrapping-keys key=$keyArn \
--metadata-output /tmp/metadata \
--encryption-context purpose=test \
--commitment-policy require-encrypt-require-decrypt \
--output .
// encrypt succeeded
aws-encryption-cli --decrypt \
--input hello.txt.encrypted \
--wrapping-keys key=$keyArn \
--metadata-output /tmp/metadata \
--encryption-context purpose=test \
--commitment-policy require-encrypt-require-decrypt \
--output .
// decrypt succeeded
// Check aws-encryption-sdk version
python -m pip list | grep “aws-encryption”
// output: aws-encryption-sdk 3.1.1
// output: aws-encryption-sdk-cli 4.1.0Trying this on a Debian EC2 Instance:
sudo apt update; sudo apt full-upgrade;
sudo apt-get install python3-venv;
mkdir temp; cd temp;
python3 -m venv venv; // The rest of the script from above.Both trials succeeded. In both cases, python -m pip list | grep “aws-encryption” reported the
same versions of the ESDK-Python and ESDK-CLI that you are using.
On Debian, I used Python 3.9.2. On Mac, I used Python 3.9.13.
So I cannot immediately re-create your issue.
Can you tell me what version of Cryptography you are using?
python -m pip show cryptography
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. Can you try running the ESDK-CLI in a clean Python virtual environment?
It could be that other packages on your host are requiring a different version of Cryptography or other dependency that is interfering with the ESDK’s dependencies.
This issue is pending a reply from @mpalmer answering the above questions.
Much Obliged, AWS Crypto Tools
mpalmer
Problem:
Simple command, taken straight from the fine manual:
When run with
aws-encryption-sdkv3.1.0, this command succeeds. When run withaws-encryption-sdkv3.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.