Day 7 of 1060 minShell Walker
Day 7: Media Provenance and Content Credentials
Taught by Mr Elite Updated
By the end of today you can
- Explain the difference between ordinary metadata and signed provenance
- Run c2patool and read a manifest, its assertions and its validation result
- Show what a broken signature and a stripped manifest look like
- Write a fair statement about what a present or missing credential does and does not prove
Warm-up
Answer from memory first, then tap to check. Recalling yesterday is what makes it stick.
Why does phone or voicemail compression lower your confidence when you compare audio spectrograms?
Compression removes or imitates many of the clues, such as high-frequency detail and background noise, so the evidence is weaker.
Before comparing two audio files, what two properties should you match?
Sample rate and number of channels.
A manager forwards you a photo of a flooded car park and asks whether it is genuine. Yesterday you would have looked for artefacts and rated each one. Today there is a different route. Some files carry a signed record of where they came from and what was done to them, and you can check that record in seconds.
The catch is that this record is easy to lose and easy to misread. A file with no record is not automatically fake, and a file with a record is not automatically true. By the end of today you will read these records with c2patool and say exactly what they prove, and what they leave open.
Metadata versus signed provenance
On Day 2 you pulled EXIF and container metadata out of files with ExifTool. That data is just text written into the file. Anyone with a hex editor or ExifTool can change the camera model, the date or the software tag, and nothing will complain. It is a clue, never a guarantee.
Provenance means a documented history: who made this, with what, and what happened afterwards. C2PA (Coalition for Content Provenance and Authenticity) is an open standard that makes that history tamper-evident. The history is bundled into the file and cryptographically signed. If someone changes the pixels or the history afterwards without re-signing, the check fails. Tamper-evident does not mean tamper-proof. It means changes show up.
- Manifest
- The signed bundle of provenance data attached to a file.
- Content Credentials
- The public name for C2PA provenance as users see it, often shown as a small 'CR' icon.
- Signer
- The person or organisation whose certificate signed the manifest, such as a camera maker or editing tool vendor.
- Hash binding
- A fingerprint of the file content stored inside the manifest, so any change to the content no longer matches.
Quick check
A photo has EXIF data saying it was taken on a particular phone. A C2PA manifest says the same. What is the key difference?
Both can state the same facts, but only the manifest is signed and hash bound. Note that it can still be removed, which matters later.
What is inside a manifest
A file can hold a manifest store, which contains one or more manifests. Each manifest describes one stage in the file's life. When an editor opens a signed photo and saves it, the editor adds a new manifest that points back to the earlier one. That chain is the edit history.
Inside each manifest you will meet these parts. Assertions are the claims, for example the actions taken (created, cropped, colour adjusted) or that generative AI was used. The claim collects those assertions and the hash bindings. The signature covers the claim and comes with a certificate chain that says who signed it. When you read output, match each statement to one of these three parts.
Install c2patool and get two test files
c2patool is the free command line reader for C2PA. Everything today runs on your own machine against sample files, not anyone else's systems. First install it.
mkdir -p ~/day07 && cd ~/day07
c2patool --versionWatch me do it: read, break, strip
Now I will read a signed file, damage a copy to see the signature fail, then strip the manifest from another copy. Run these with me inside day07. Always work on copies and keep the original untouched, and hash it first as you did on Day 1.
import shutil
from PIL import Image
shutil.copy('C.jpg', 'broken.jpg')
data = bytearray(open('broken.jpg', 'rb').read())
data[len(data) - 2000] ^= 0xFF
open('broken.jpg', 'wb').write(data)
Image.open('C.jpg').convert('RGB').save('resaved.jpg')Notice the difference between the two failures. The broken copy still contains a manifest, but the check says the content was altered after signing. The re-saved copy has no manifest at all, so there is nothing to check. Those two outcomes mean very different things in a report.
Quick check
broken.jpg reports a data hash mismatch. What have you actually established?
A mismatch only says the content no longer matches what was signed. It does not say why it changed or whether the change was malicious.
Your turn: two files, two honest write-ups
No lab today, so the practice is on your own machine with the files you gathered. You will run c2patool on the signed sample and on plain.jpg, then fill in a small table in notes07.md. Use this layout so your reasoning is easy to review.
## File: C.jpg
SHA-256:
Manifest present: yes/no
Signer / issuer:
Claim generator:
Actions listed:
Validation result:
What this shows:
What this does NOT show:Take care with the trust question. A manifest can validate (the signature is mathematically correct and the content matches) yet the signer's certificate may not be on a trust list your tool knows about. Newer c2patool versions separate these states. Record exactly what your version says, and do not upgrade the wording to 'verified authentic'.
What a missing credential means
Most images on the internet have no credentials. Many cameras and tools never add them. Social platforms and messaging apps often strip metadata and manifests when they recompress an upload. Screenshots remove them entirely. So a missing credential is the normal state of the world and carries almost no weight on its own.
A present, valid credential is stronger evidence, but only about what it claims. It can show that a particular tool signed this content at a particular time and that nothing changed since. It cannot show that the scene was real, that the person using the camera was honest, or that a signer's key was never stolen. Treat it as one signal alongside everything from Days 2 to 6.
Quick check
A viral photo has no C2PA manifest. Which statement is the most defensible?
Stripping happens routinely and many sources never sign, so absence tells you very little.
If it did not work
Treating a missing manifest as evidence of a fake
Remember that platforms, screenshots and editors strip manifests all the time. Record it as 'no provenance available' and move on to other evidence.
Reading 'valid signature' as 'the image is true'
A valid signature proves the content is unchanged since signing and shows who signed it. It says nothing about whether the scene was staged or the signer lied.
Testing on your only copy of the evidence
Hash the original, work on copies, and name each copy clearly so your notes match the files.
Ignoring the trust status of the signer
Note the issuer and whether your tool reports the certificate as trusted. A valid but unknown signer is weaker than a known one.
Recap
- Ordinary metadata is editable text; C2PA manifests are signed and hash bound, so changes are detectable
- A manifest holds assertions, a claim and a signature, and can chain back through earlier edits
- c2patool file reads a manifest and reports validation results
- A hash mismatch means the content changed after signing, not that it is malicious
- A missing manifest is neutral because stripping and non-signing are common
- State what a credential shows and does not show, with a confidence level
Cheat sheet
c2patool --version- Confirm the tool is installed
c2patool file.jpg- Print the manifest store and validation results as JSON
c2patool file.jpg --detailed- Show lower level detail where your version supports it
c2patool file.jpg --tree- Show the chain of manifests and ingredients
Manifest- Signed bundle of provenance data
Assertion- A single claim, such as an action taken or AI use
Hash mismatch- Content differs from what was signed
No claim found- No manifest present, which is neutral
Before the next day
Mission: Credential or not: two files, two honest answers
Run c2patool on a file with credentials and one without, then write up what each result does and does not tell you. This builds the habit you need for Day 8, where you must state findings with a confidence level.
About 30 min
You are done when: A day07 folder with the original and copied files, the saved c2patool output, and notes07.md covering all four files.
Want more? Upload C.jpg to the free Content Credentials verify web page from the Content Authenticity Initiative, compare its display with your c2patool reading, and note any differences in wording. Only use sample files you are happy to upload.
Quiz
4 questions. Your score is saved with your progress.
1. What makes a C2PA manifest more reliable than EXIF metadata?
The signature and hash binding make changes visible. EXIF carries neither.
2. You re-save a signed image through an editor that does not support C2PA and c2patool finds no manifest. What is the best explanation?
Tools that do not preserve manifests simply drop them on save. That is a loss of provenance, not evidence of forgery.
3. A manifest validates and names a known signer. What can you conclude?
Validation covers integrity and signer identity only. It does not cover truthfulness of the scene or key security.
4. Which sentence belongs in a defensible report?
It records the observation, avoids overreach and points to the evidence that carries the conclusion.
Finish the day
Mark the day complete to save your progress.
Next: Day 8 turns your toolkit into a process: take a report, gather and hash evidence, run the checks from Days 2 to 7, and write findings with a stated confidence level. Today's careful 'shows and does not show' habit is the core of that report.
Your notes
Private to this device. Write what you want to remember from today.