crypto-js | fairly trivial modifications in 2.x-old-scintill branch

Can you try something like this :-

The error message seems fairly straight-forward to me: the key size you used isn't supported by that library. In fact, you appear to have only pasted part of the message, which goes on to list the key sizes which are supported: https://github.com/phpseclib/phpseclib/blob/7e38313802b62606cf27ddf573a7c47e88b5d33f/phpseclib/Crypt/AES.php#L118

'Key of size ' . strlen($key) . ' not supported by this algorithm. Only keys of sizes 16, 24 or 32 supported'

So your problem is not understanding what the PHP can do, but understanding what the JS is doing with your input.

The clue to that is in the CryptoJS docs:

CryptoJS supports AES-128, AES-192, and AES-256. It will pick the variant by the size of the key you pass in. If you use a passphrase, then it will generate a 256-bit key.

So the library agrees that there are three valid key lengths, but supports passing in a "passphrase" instead which will be used to generate a key. The exact algorithm it uses to do that isn't documented; presumably it uses some Key Derivation Function with fixed parameters, so that the same passphrase will always produce the same key. If you really need to emulate it, you'll need to trace through the source code.

If you just need code that's compatible with both libraries, generate a random key of one of the supported lengths, and use that in both places.

Key, IV and ciphertext are hex encoded and therefore must be parsed with the hex encoder and converted to WordArrays (also CryptoJS applies a key derivation function if the key is passed as a string).

The ciphertext must be passed as a CipherParams object.

CTR is a stream cipher mode and does not use padding. In CryptoJS padding must be explicitly disabled, otherwise the default padding (PKCS7) is applied.

The easiest way to explain this is with an example. The following key pair is used for the example:

Add this line before RUN npm install:

try to use a boolean, so onDestroy you cast this.destroy$.next(true). i'm following this guide

https://www.digitalocean.com/community/tutorials/angular-takeuntil-rxjs-unsubscribe

your mongodb Client is running on your local machine you must make a cloud base mongodb cluster like Atlas and change your mongo URI with cloud base cluster URI.

I figured it out. Simple human error. customDate return today's date in this format, 2021-05-25 08:20:02 but this is the expected format, 2021-5-25 8:20:2. Single digits when the number is less than 10.

I replaced the customDate function with this:

You're missing the corresponding python steps to prepare the data, from hex and b64