C2PA's Worst Case Scenario - The Hacker Factor Blog
hackerfactor.com · 4,051 words · saved by 1 readers
Copyright 2002-2025 Hacker Factor. All rights reserved.
A month ago, I wrote a very detailed and critical review of the Coalition for Content Provenance and Authenticity (C2PA) specification for validating media metadata. My basic conclusion was that C2PA introduces more problems than it tries to solve and it didn't solve any problems. Although a few people have left comments on the blog, I have had a near daily stream of new contacts writing in. Some are curious developers, while others are people tasked with evaluating or implementing C2PA. The comments have come from small organizations, Fortune-500 companies, and even other CAI and C2PA…
saved by
related reading
- Using ZK Proofs to Fight Disinformation | by Dan Boneh | Mediummedium.com
- The Compute Verification Postfirstscattering.com
- Digital hygiene – karpathykarpathy.bearblog.dev
- The Compute Verification Postsubstack.com
- The Letter - Stop Hacklore!hacklore.org
- When AI Writes the World's Software, Who Verifies It? — Leonardo de Mouraleodemoura.github.io
- Would you fly on an AI-coded plane | Hackle's bloghacklewayne.com
- Product Security Bad Practicescisa.gov
- Themes from Real World Crypto 2022 - The Trail of Bits Blogblog.trailofbits.com
- Concrete Evaluations to Investigate the OpenAI Model That Hacked Hugging Face — LessWronglesswrong.com
- Degraded Blockchainsfortressofdoors.com
- Cryptographic right answers | Latacoralatacora.com