Why do you need to hash your files? Let’s start with that.
You need to hash your files so that you can guarantee that none of your files have been altered. This is a way to make your delivery trustable. Let’s say you are delivering a file, any kind of file like an executable of source code using a disk to a friend or to your customer, in order to make sure that the file(s) in your package has not been tampered with, you need to hash your files and provide the hash along with the contents. In Windows, there is a very small and easy to use command line utility for this. It is called FCIV(File Checksum Integrity Verifier). FCIV supports both MD5 and SHA1 hash algorithms.
It is very easy to setup and use. Here is how you can use File Checksum Integrity Verifier to generate hashes for your files:
1- Go to https://support.microsoft.com/en-us/help/841290 and download the installation file
2- Create a folder
3- Double-click the FCIV executable and browse to the folder you created and extract the files here
3- Add this folder to your system path variable
If FCIV was installed to the C:\FCIV directory, type set path=%path%;c:\fciv to add it to the system path in a command shell.
4- Now you can create MD5 hash for a file or archive easily:
Default hash algorithm is MD5.
Here is the FCIV syntax:
fciv.exe [Commands] <Options>
|-add <file | dir>||Compute hash and send to output (default screen).|
-r : recursive.
-type : ex: -type *.exe.
-exc file: list of directories that should not be computed.
-wp : Without full path name. Default store full path.
-bp : specify base path to remove from full path name.
|-list||List entries in the database.|
Option: -bp basepath.
|-md5 | -sha1 | -both||Specify hashtype, default md5.|
|-xml db||Specify database format and name.|
Hope this helps.