Skip to content

Instantly share code, notes, and snippets.

@kenichi-shibata
Forked from aklap/checking_shasums.md
Created December 4, 2021 23:40
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kenichi-shibata/2191c8d01f2c8374d219418ffaf0051d to your computer and use it in GitHub Desktop.
Save kenichi-shibata/2191c8d01f2c8374d219418ffaf0051d to your computer and use it in GitHub Desktop.
How to check a file's shasum

##How to check file integrity with shasum


For verifying the integrity (but not authenticity of data, i.e., who authored it or the origin of the file) of a file, it is necessary to run a checksum function on the file which will output a value and compare it to a previously stored checksum value; if it matches we can be relatively confident that the file hasn't been tampered with or altered.

You might be asked to verify a file's sha1sum or sha2sum–all this means is calculating and verifying the cryptographic sha1 or sha2 hash value or digest included in the file.

###Various commands and methods for verifying shasum 1 or 2:


Organic:
In terminal run:

For sha2:
shasum -a 256 filename/path

For sha1:
shasum -a 1 filename/path

Use your eyeballs and compare by sight the expected hash and the computed hash in the terminal. Eye strain might ensue.

Artisanal & organic:
Run the above commands. Copy the resulting shasum with Ctrl + C. In browser or file use Ctrl + F with your copied shasum; if you find a match, congrats your file is fine! If no match, your file might have been altered or tampered with.

Inorganic, man-made:
Use shasum check command. Runs diff and prints results in terminal.

In terminal run:
echo 'your_expected_shasum_here_followed_by_a_space *name_of_file_to_check_after_asterisk' | shasum -c

####References:

Someone in China

Raspberry Pi Forums

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment