Exercise 10 submission
Name or course identifier:
Environment and original observation
- Node version, browser, and repository or student kit:
- Genuine update result and current announcement before tampering:
- Harmless change made to the payload:
- Inspection before recomputing: checksum match / publisher signature valid:
- Starter result when applying the changed payload with the original checksum (before recomputing), and whether the current announcement stayed unchanged:
- Inspection after recomputing: checksum match / publisher signature valid:
- Starter result when applying the rehashed tampered update:
- Why the matching checksum did not prove a trusted publisher:
Include your own local response evidence or screenshots. The website simulation and supplied screenshots are examples, not evidence that your edited app works.
Repair
Paste your changed update-policy.mjs. Explain the helper's decision and where its trusted public key comes from. Explain why a publicKey field supplied by an update cannot establish trust. Confirm that you changed only the policy file.
Verification evidence
Confirm you saved, stopped and restarted the server, and refreshed after editing. Collect the first three rows without another restart or reset.
| Scenario | Actual result or HTTP status | Current title, message, and version |
|---|---|---|
| Genuine publisher update after repair | ||
| Rehashed tampered update after repair | ||
| State compared with the genuine update after rejection | ||
| Second genuine publisher update | ||
| Same genuine update applied again |
For the rejected update, record that the checksum matched but the publisher signature was invalid. Attach your own screenshots or response evidence. Paste the actual node checks.mjs output, including its final count; explain any failures.
Explanation
- How does an untrusted accompanying checksum differ from a signature checked with a trusted public key?
- Which key stays private, and which key belongs in the app? Why does recomputing a checksum not require either key?
- Why can changing whitespace invalidate a signature even when the JSON still means the same thing?
- Why are both genuine acceptance and unchanged state after rejection necessary evidence?
- Explain why genuine replay is permitted here and whether an authentic update necessarily means a fresh update. Name one concern this lesson leaves outside scope.