sha1 | name sha1init | Hashing library

A base32 encodes every 5 bits of input bytes into base32 character, go base32 use The RFC 4648 Base 32 alphabet (A-Z, 2-7). When decode a string to bytes, each base32 character input will be mapped to a 5 bit index then recompose to bytes.

In your example "VEV2QJEAUN453SR4Q4H3AIS4CI", the previous "VEV2QJEAUN453SR4" was already valid input, it is a 16 char input, and 5 bit * 16 is 80 bit so it can be resolved into 10 bytes output. Now let us just look at the rest "Q4H3AIS4CI", 10 char -> 5 * 10 = 50 bits, the previous 40 bits can be decode to 5 bytes, but the last 2 char "CI" leads 2 bit remainder

There are more ways to detect that the container is running under the emulation, however the most reliable way is to use identify if the entry point is emulated.

When a container is created, the entry point will become the PID 1. The mechanism that Docker uses for the qemu emulation will detect that the entry point is for a different architecture and will involve the emulator to emulate the architecture. You can read more about the mechanism used in this post.

Since the entry point will be emulated, the process name will be replaced with the qemu-xxxx where the xxxx is the architecture that will be emulated. We can identify if our entry pint process was substituted for qemu if we call ps -uax as in the following example:

Simply decoding to the struct and encoding again will satisfy your goal.

Please check this: https://go.dev/play/p/69vjlve4P6p

PasswordProtection is an inner class of java.security.KeyStore. To instantiate it in Lucee you need to use a $, so change

This is how I would do it, it's more code than what you already have but I believe should do what you're looking for.

The firsts steps are mainly the same, gather all SHA1 hashes from both folders and construct a list of objects.
Then, on the first loop over the "difference folder" (this would be the Copy folder), filter by Unique files based on it's hashes compared to the reference folder and files where the Name of the file exists in the reference folder but it's hash has changed (this would meet the condition 2 of your question).
Lastly, the second loop over the "reference folder" to get the unique files of this collection based on the file hashes.

The $result collection would be an array of objects with a newly added property Status to help identify if the file has changed or if it's unique.

First of all, you are using a class as a namespace, and that is probably not correct. Your method call should probably look something like this:

By making MAIN a multi sub:

Finally I found a solution that worked for me. There are two major points:

SwissSign provided us with the certificates for our staging environment (pem and key file) and we created the p12 file on our own.

By specifying the OpenSSL parameter CSP when creating the p12 file, the correct CSP can be set. A command might looks like:
openssl pkcs12 -export -out Output.p12 -inkey My.key -in My.chain.pem -name My -CSP "Microsoft Enhanced RSA and AES Cryptographic Provider"

In case you only have the p12 file, you have to convert it from PKCS10 into PEM format before by calling:
openssl pkcs12 -in my.p12 -out my.pem

As mentioned earlier, the following AppContext switches have to be set:

i wanted to post a quick update for anybody that is having the same issue, i opened a similiar question on the microsoft q&a site and looks like it's an issue on the azure side that they are working on fixing for GA Microsoft Q&A