Skip to content

Document verification of a tampered bundle - #5

Open
lntutor wants to merge 1 commit into
HenryParker37-VIP:mainfrom
lntutor:docs/4-tampered-bundle-example
Open

Document verification of a tampered bundle#5
lntutor wants to merge 1 commit into
HenryParker37-VIP:mainfrom
lntutor:docs/4-tampered-bundle-example

Conversation

@lntutor

@lntutor lntutor commented Jul 31, 2026

Copy link
Copy Markdown

Summary

  • add a copy-safe walkthrough that modifies stdout.txt in a disposable bundle
  • show the expected integrity failure, tampered-file status, and exit code
  • clarify that the example does not bypass ReproSpec security boundaries

Validation

  • npm test (command passes; repository currently discovers 0 tests)
  • ran the documented capture, copy, tamper, and verify commands
  • verified reprospec verify exits 1 and reports stdout.txt: TAMPERED
  • git diff --check

Fixes #4

@lntutor

lntutor commented Aug 1, 2026

Copy link
Copy Markdown
Author

Current head 227b3f94e4e8e97068ff36eb8f6b1178c0a35eec is mergeable. This PR is scoped to QUICKSTART.md, adding documentation for verifying a tampered bundle. There are currently no review comments or visible failing checks attached to this head. Please review when convenient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] Add usage examples of ReproSpec verify command on tampered bundles in QUICKSTART.md

1 participant