The Checksum at the End

Written by Studio AM.

A file can change while it is stored or sent. A damaged cable, failing device, or incomplete transfer may alter data without leaving a visible tear. A checksum helps reveal that change.

A program follows a fixed rule to calculate a short value from the file's contents. The sender records that value. After transfer, the receiver applies the same rule again. Matching values provide evidence that the data arrived unchanged; different values show that something is wrong.

A simple checksum cannot identify every possible change, and two different files can sometimes produce the same value. Long, well-designed cryptographic hashes can make accidental matches extremely unlikely. Checking against deliberate tampering also requires a trustworthy reference value.

The checksum is not a spare copy of the file. It is a compact test. Like a total written at the bottom of a list, it lets the receiver check consistency without comparing every item by eye.

Questions

Choose an answer. The explanation appears after you answer.

  1. Question 1 of 4

    What is the main idea of the passage?

  2. Question 2 of 4

    Why must sender and receiver use the same rule?

  3. Question 3 of 4

    What does “compact” mean in the final paragraph?

  4. Question 4 of 4

    What indicates that something is wrong?

Score: none answered yet.

More passages

Practise reading