back to labs
Integrity: Find the Tampered File with sha256sum -c
EasyCommand Line Essentials10-15 minThe brief
A directory of config files ships with a SHA256SUMS manifest, but one file was modified after the manifest was made. Using /root/case/dist, report in three plain-text files (not directories), one answer each:
/root/case/tampered.txt— the name of the file that fails verification, e.g.name.conf(thename.conf: FAILEDlinesha256sum -cprints is accepted too)/root/case/okcount.txt— how many files verify OK, as a number/root/case/total.txt— how many files were checked in total, as a number
The file set and which one is tampered vary per session. See /root/case/brief.txt.
What you'll do
- Verify a set of files against a SHA256SUMS manifest
- Read `sha256sum -c` output (OK vs FAILED)
- Identify a tampered/corrupted file
- Summarize an integrity check
Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.
