Also descovered that the wrong hex of the decrypted file was being returned in the TripleDES algorithm. After verifying the decrypted data, I validated that the returning decrypted string is equivalent to the contents of the file so the calcuated hash was originally wrong.
Also descovered that the wrong hex of the decrypted file was being returned in the TripleDES algorithm. After verifying the decrypted data, I validated that the returning decrypted string is equivalent to the contents of the file so the calcuated hash was originally wrong.

dcjulian29/toolkit