phpseclib | PHP Secure Communications Library | Cryptography library

You're trying to install phpseclib v3 using the instructions for phpseclib v2. There are two options:

Option 1: Use PHPSecLib V3 With Composer

This option requires SSH access on the server.

To install phpseclib v3 you're gonna need Composer. Once you have that installed you can do composer init and then composer require phpseclib/phpseclib:~3.0.

By doing that you can replace this:

You need to use PKCS1 padding. eg.

There are issues in both codes:

• By default phpseclib uses PSS as padding (here and in the following v3 assumed). Padding is explicitly set to PKCS#1 v1.5 though, but it is not used because the return value is not applied. For the padding change to take effect, the return value must be considered.
  By the way, SHA256 is the default here. And RSA::ENCRYPTION_PKCS1 is ignored in the context of signing/verifying and can be removed as well.

• phpseclib hashes the data implicitly when signing. Since in the current phpseclib code the hash is additionally generated explicitly, double hashing is done. This double hashing is not necessary and can be removed.

• The double Base64 encoding at the end is also unnecessary and can be removed as well.

  Overall:

RS256 in Java means RSASSA-PKCS1-v1_5 using SHA-256

The posted Python (PyCryptodome) and JavaScript (JSEncrypt) reference codes do the following:

• Generation of a timestamp (number of milliseconds elapsed since January 1, 1970 00:00:00 UTC).
• Concatenation of timestamp and token in the format +.
• Encryption with RSA and PKCS#1 v1.5 padding (RSAES-PKCS1-v1_5)
• Base64 encoding and subsequent URL encoding

The posted PHP code uses different libraries for encryption: phpseclib (V3 and V1) and OpenSSL. The only difference from the reference code turned out to be that the timestamp is determined in seconds (instead of milliseconds), which was eventually identified as the cause of the problem.

The rest is consistent with the reference code, including the encryption with RSA and PKCS#1 v1.5 padding originally suspected as the cause of the bug, as could be easily verified by using a valid key pair and decrypting the ciphertext generated with the PHP code with a second independent application (e.g. online).

Note that phpseclib V3 specifies PKCS#1 v1.5 padding in the context of encryption with RSA::ENCRYPTION_PKCS1.

In the C# code PKCS#1 v1.5 padding is applied (2nd parameter of Encrypt() is false), phpseclib uses OAEPadding by default (here).

Decryption works if PKCS#1 v1.5 padding is explicitly specified in the PHP code:

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.

The BigInteger class has a toHex() method. So you can get the hex value like this:

The new logging style comes from the BuildKit features.

You can disable this in the Docker Desktop GUI:

1. select the Docker Engine tab
2. set "features"{ "buildkit" : false }

Then if you want to use the logging features again, you can run with DOCKER_BUILDKIT=1. I believe you can run with DOCKER_BUILDKIT=0 if you want to selectively disable but haven't tested that yet.

Of course, be aware that you'll lose out on the following features that BuildKit adds to Docker:

• Docker images created with BuildKit can be pushed to Docker Hub just like Docker images created with legacy build
• the Dockerfile format that works on legacy build will also work with BuildKit builds
• The new --secret command line option allows the user to pass secret information for building new images with a specified Dockerfile