HashFile

Estimated reading: 5 minutes 1762 views

This activity enables users to create a unique hash value for an input file. The hash value serves as a digital fingerprint, ensuring the file’s integrity and authenticity. Hashing is particularly useful for checking that a file hasn’t been modified, as even a tiny change in the file’s content will generate a completely different hash value.

Points to note

1. To generate a unique hash value for the provided file, a “Secret” key is required for the following algorithm types: 
a. HMAC using MD5 (Deprecated)
b. HMAC using SHA-1 (Deprecated)
c. HMAC using SHA-256
d. HMAC using SHA-384
e. HMAC using SHA-512
2. There is no minimum character requirement for the “Secret key” for the above algorithm types.
3. The “Secret key” parameter will not appear in the properties section when using any of the above algorithm types. Instead, you will find the option within the activity when you double-click on it.

Properties

INPUT

Algorithm: This parameter indicates to choose the algorithm type from the drop-down menu that is used to generate the hash for the file based on it.

1. HMAC using MD5 (Deprecated)
2. HMAC using SHA-1 (Deprecated)
3. HMAC using SHA-256
4. HMAC using SHA-384
5. HMAC using SHA-512
6. SHA-1
7. SHA-256
8. SHA-384
9. SHA-512

Refer to the documentation below to view the types of algorithms.

By default, the activity recommends the most commonly used type, ” HMAC using SHA-256”.

DelayAfter: It assists the user to add a delay before initiating subsequent activities. The delay duration here is in milliseconds. By default, it is set to “1000” milliseconds.
When the option is left blank, the delay will not be considered.

DelayBefore: It assists the user in adding a delay before starting the execution of the activities. The delay duration here is in milliseconds. By default, it is set to “1000” milliseconds.
When the option is left blank, the delay will not be considered.

Input File Path*:  This parameter indicates the input path of the file for which the hash value needs to be generated.

It accepts values in the “String” datatype. You can either hardcode the values in “String” format or provide a variable in “String” datatype.

Key Encoding: It assists the user to choose the key encoding type from the drop-down menu that is used to perform the encryption algorithm.

Click here to refer the documentation to view the types of key encoding.

By default, the activity recommends the most commonly used type, “Unicode UTF-8”.

MISC

DisplayName: Displays the name of the activity. The activity name can be customized, which aids in troubleshooting.

SkipOnError: Specify the “Boolean” value as “True” or “False.”

True: Continue executing the workflow regardless of any errors thrown.
False: Halt the workflow if it encounters any errors.
None: If the option is left blank, the activity will, by default, behave as if “False” were chosen.

Version: It indicates the version of the feature being used.

OUTPUT

Hash: It assists the user to declare a variable to view the output of the activity as the “HASH” value generated for the provided input file. 

This field returns values in “String” datatype. You can either hardcode the values in “String” format or can provide the variable in “String” datatype.

Result: It provides the ability to view the execution status of the activity. It returns values in “Boolean.”

True: Indicates that the activity has been executed successfully without any errors.
False: Indicates that the activity has been unsuccessful due to an unexpected error being thrown.

Represents mandatory fields to execute the workflow.

Types of Algorithms

Below are detailed explanations of the types of algorithms and their status:

1. HMAC using MD5 (Deprecated):
a. HMAC (Keyed-Hash Message Authentication Code) using MD5 is a cryptographic hashing algorithm. It combines a secret key with the MD5 hash function to generate a unique hash value.
b. Status: Deprecated due to vulnerabilities. Not recommended for new implementations because of collision vulnerabilities.
2. HMAC using SHA-1 (Deprecated):
a. HMAC using SHA-1 combines a secret key with the SHA-1 hash function to produce a hash value.
b. Status: Deprecated due to vulnerabilities similar to MD5. It’s not recommended for security-sensitive applications.
3. HMAC using SHA-256: 
a. This algorithm utilizes SHA-256 (Secure Hash Algorithm 256-bit) for hashing alongside a secret key.
b. Security: Offers stronger security compared to MD5 and SHA-1 due to SHA-256’s enhanced collision resistance.
4. HMAC using SHA-384:
a. This variant employs SHA-384, a member of the SHA-2 family, for hashing with a secret key.
b. Security: Provides higher security and collision resistance compared to SHA-256 due to its longer hash size (384 bits).
5. HMAC using SHA-512:
a. This algorithm utilizes SHA-512, another SHA-2 variant, for hashing alongside a secret key.
b. Security: Offers the highest level of security and collision resistance among the listed HMAC algorithms due to its longer hash size (512 bits).
6. SHA-1:
a. SHA-1 (Secure Hash Algorithm 1) produces a 160-bit hash value from input data.
b. Status: Deprecated for security-sensitive applications due to vulnerabilities. Still used in legacy systems but not recommended for new implementations.
7. SHA-256:
a. SHA-256, part of the SHA-2 family, generates a 256-bit hash value, providing stronger security and collision resistance compared to SHA-1.
b. Security: Widely adopted for security-sensitive applications and digital signatures.
8. SHA-384:
a. SHA-384, another SHA-2 variant, produces a 384-bit hash value, offering higher security than SHA-256 due to its longer hash size.
9. SHA-512:
a. SHA-512 is the 512-bit variant of SHA-2, providing the highest level of security and collision resistance among the SHA algorithms listed.
b. Security: Suitable for applications requiring maximum security, such as secure communication protocols and digital certificates.

Share this Doc

HashFile

Or copy link

CONTENTS