Build a Termux Package Integrity Baseline
Capture trusted package sources, installed versions, and hashes for selected local configuration files, then define a repeatable way to detect unexpected changes.
Capture trusted package sources, installed versions, and hashes for selected local configuration files, then define a repeatable way to detect unexpected changes.
Prepare 25m · Build 105m · Verify 25m · Document 25m
Work only inside the folder created by Smartphone-Academy.py prepare package-integrity-baseline. Use the supplied fictional samples or data you are explicitly authorized to handle.
Prepare the Termux workspace
Open Termux in the Academy folder and create the safe workspace. The companion generates samples, notes, and evidence files under your account.
python Smartphone-Academy.py prepare package-integrity-baselineNo root. Work only with the supplied files under $HOME.Practical mission
- Export installed package names and versions without including personal device identifiers
- Record configured Termux repositories and the result of a safe update check
- Hash selected local configuration files and explain what a changed hash can and cannot prove
- Write a repeatable monthly verification routine with a rollback note
A package-baseline.md with package-list.txt, repository notes, selected configuration hashes, and a monthly verification checklist.
Quality gate
Analyst reflection
Which result from “Write a repeatable monthly verification routine with a rollback note” needs additional evidence before it could support a real operational decision?
After checking the deliverables, run python Smartphone-Academy.py complete package-integrity-baseline. Progress is stored locally in the Termux home directory.