>_ IzzyLab

Topic breakdown

A checksum is a fingerprint of the contents: change even a single byte and the hash changes too. It catches accidental corruption of a file, but doesn't protect against tampering (anyone can recompute the hash) — for that you need a signature. The sha256sum utility prints a line "hash␠␠filename" in exactly the format that the -c check mode later understands; the output is redirected into the target file. The main subtlety is the path: the line gets exactly the name that was passed, so a relative name obliges you to run the check from the same directory too.

What's checked

  1. sha256sum -c passes without errors
  2. the file has the sum of the original release.bin

What it looks like