Hash256 | simple python program that uses sha256 | Hashing library

By making MAIN a multi sub:

hexdigest() contains only hexadecimal digits. You need to return the digest of the strings passed

So far: I found in the documentation an important note:

NOTE!

 In the columns parameter; you should:

1. Open brackets.

2. Put a “comma” then a “space” between the columns value.

Example: columns=[acquirer_name, authorization_code, amount, bin_number]

 In the filters parameter; you should:

1. Open brackets.
2. Then open a curly brackets.
3. Write the “key”
4. Put a “comma” then a “space.
5. Write the “value” of the key.

^{(I originally marked this as a duplicate of Difference between SHA256CryptoServiceProvider and SHA256Managed - however this question is specifically in the context of ASP.NET Core 3.x which isn't the same as the linked question (.NET Framework on Windows).)}

You're conflating two different things:

• SHA256 represents the 256-bit flavor of the SHA-2 cryptographic hasing function, while, SHA256Managed, SHA256CryptoServiceProvider and SHA256Cng are its implementations.

• SHA512 represents the 512-bit flavor of the SHA-2 cryptographic hasing function, while, SHA512Managed, SHA512CryptoServiceProvider and SHA512Cng are its implementations.

The differences between the 256-bit and 512-bit versions of SHA-2 are documented on Wikipedia. Note that .NET does not support the 224-bit version, but does support the 256, 384 and 512-bit versions.

Regarding the differences between SHA{bits} (the interface) and SHA{bits}Managed, SHA{bits}CryptoServiceProvider and SHA{bits}Cng:

• The .NET Framework and .NET Core support multiple different implementations of the same hashing algorithms, this can be because some implementations may be hardware accelerated, provided by the operating system, or implemented entirely in C#/Managed-code.
• SHA256 is an abstract base class that defines the interface of all implementations of the SHA-2 (256-bit) hashing function. Ditto SHA512 for the SHA-2 (512-bit) function.
• SHA256Managed (and SHA512Managed) are 100% C#/Managed-code implementations that do run slowly compared to native or OS-provided implementations. This is the only implementation provided that's built-in to .NET Core.
• SHA256CryptoServiceProvider and SHA256Cng are OS-provided implementations that may be used for faster performance or for FIPS compliance (as SHA256Managed is not FIPS compliant). If you don't know if you need to worry about FIPS compliance then you probably don't need to worry about it (i.e. unless you're working for the US federal government or your company's legal team has informed you of your project's regulatory compliance requirements).
  • Additionally, SHA256CryptoServiceProvider and SHA256Cng are not built-in to .NET Core, only .NET Framework.
• The SHA256.Create() method is a factory method that is meant to return the "best" implementation for the current platform - in .NET Core it always returns an instance of SHA256Managed.