pycryptodome | A self-contained cryptographic library for Python | Cryptography library

If you read the documentation you will see that encrypt_and_digest() is only supported by the modern modes:

• MODE_CCM
• MODE_EAX
• MODE_GCM
• MODE_SIV
• MODE_OCB

ECB mode really shouldn't be used for anything as it is not semantically secure.

First of all, for the OpenSSL command line, the key (-K option) and IV (-iv option) must be supplied with hexadecimal values. If we supply your values they are short they are padded with 0s with a warning;

I want to configure the state to perform a certain action if curl returns an error.

There is a Salt state called http which can query a URL and return the status. Using this (instead of curl) we can check for the status code(s) (200, 201, etc.), as well as matching text. Then we can use requisites to run subsequent states depending on the success/failure of the http.query.

Example:

I have added a check for status code of 200, you can omit - status: 200 if you don't care about the status code.

There are two core issues:

On the node side, you're treating the output of Python as if it's a UTF-8 string. Node will treat it as a UTF-8 string, and the resulting bytes that make up the Buffer are going to be wrong. Dump it out, you'll see it's a 25 byte buffer, not what you intended.

Once you fix that, you'll find the second issue. The crypto library expects padding bytes, even if the only block is exactly the block size. To fix this, always add padding to the plaintext.

So, the encrypt changes to this:

It looks like there's a problem in the version of pycrypto/pycryptodome that you're installing. The lines prior to the one in your question should contain details about what this is. It could be that this distribution doesn't work on windows, doesn't specify all the dependencies it needs or one of many other problems. If you can post the entire error we should be able to give more advice.

You could try installing an early version to see if that works, the current version of pycryptodome is 3.10.1 so try pip install pycryptodome==3.9.9 which is the previous version in PyPI.

Another thing you can do is install the distribution a different way. Try downloading the .tar.gz archive of the package and pip installing that file e.g. pip install pycryptodome-3.10.1.tar.gz

Both of these solutions may work but it's impossible to say without knowing the precise problem with the install.

On pycrypto github there seem to be a lot of installation problems and the recommendation is) to use pycryptodome instead.

From my experience, the most relable way to include dependencies to lambda functions is through lambda layers and the use of docker as described in the AWS blog.

Thus you can add pycrypto to your function as follows:

1. Create empty folder, e.g. mylayer.

2. Go to the folder and create requirements.txt file with the content of

You have two problems here...

The primary problem is a strange one. The apt-get package tesseract-ocr-eng is installed as a transient dependency of one of the other packages you install with apt-get:

If others have to use your password to be able to use your script, it's impossible. If the computer can read it, then the user will also find a way to read it.

I recommend using a E-Mail service where the user can enter their own API key or just let them enter their own GMail credentials.

Correct me if I'm wrong, but I think there's no way to use your password in this case unless you write an API and send the E-Mail from your server. But don't forget that in this case, the user might be able to use your API as a way to send spam.

TL;DR: Let the users use their own passwords.

The decryption will be done correctly if you replace in the line