The Coalition for Content Provenance and Authenticity (C2PA) addresses the prevalence of misleading information online through the development of technical standards for certifying the source and history (or provenance) of media content. Adobe and other contributors created the C2PA Rust SDK as part of the Content Authenticity Initiative and released it to open source in June, 2022.
The C2PA Rust SDK implements a subset of the C2PA technical specification.
The SDK enables a desktop, mobile, or embedded application to:
- Create and sign C2PA claims and manifests.
- Embed manifests in certain file formats.
- Parse and validate manifests found in certain file formats.
The SDK supports several common C2PA assertions and hard bindings.
This is a beta release (version 0.x.x) of the project. The minor version number (0.x.0) is incremented when there are breaking API changes, which may happen frequently.
We welcome contributions to this project. For information on contributing, providing feedback, and about ongoing work, see Contributing.
The SDK requires Rust version 1.70.0 or newer.
The SDK has been tested on the following operating systems:
- Windows (Intel only)
- MacOS (Intel and Apple silicon)
- Ubuntu Linux (64-bit Intel and ARM v8)
- WebAssembly (Wasm)
Extensions | MIME type |
---|---|
avi |
video/msvideo , video/avi , application-msvideo |
avif |
image/avif |
c2pa |
application/x-c2pa-manifest-store |
dng |
image/x-adobe-dng |
heic |
image/heic |
heif |
image/heif |
jpg , jpeg |
image/jpeg |
m4a |
audio/mp4 |
mp4 |
video/mp4 , application/mp4 |
mov |
video/quicktime |
png |
image/png |
svg |
image/svg+xml |
tif ,tiff |
image/tiff |
wav |
audio/x-wav |
webp |
image/webp |
Add this to your Cargo.toml
:
[dependencies]
c2pa = "0.26.0"
If you want to read or write a manifest file, add the file_io
dependency to your Cargo.toml
.
The add_thumbnails
feature will generate thumbnails for JPEG and PNG files.
For example:
c2pa = { version = "0.25.0", features = ["file_io", "add_thumbnails"] }
NOTE: If you are building for WASM, omit the file_io
dependency.
The Rust SDK crate provides:
file_io
enables manifest generation, signing via OpenSSL, and embedding manifests in various file formats.add_thumbnails
will generate thumbnails automatically for JPEG and PNG files. (no longer included withfile_io
)serialize_thumbnails
includes binary thumbnail data in the Serde serialization output.xmp_write
enables updating XMP on embed with thedcterms:provenance
field. (Requires xmp_toolkit.)no_interleaved_io
forces fully-synchronous I/O; otherwise, the SDK uses threaded I/O for some operations to improve performance.fetch_remote_manifests
enables the verification step to retrieve externally referenced manifest stores. External manifests are only fetched if there is no embedded manifest store and no locally adjacent .c2pa manifest store file of the same name.json_schema
is used bymake schema
to produce a JSON schema document that represents theManifestStore
data structures.
The c2pa
crate is distributed under the terms of both the MIT license and the Apache License (Version 2.0).
Note that some components and dependent crates are licensed under different terms; please check the license terms for each crate and component for details.
In most cases, you should depend on this crate as published via crates.io.
The Adobe team produces nightly snapshots of this crate via a nightly
branch, which we use for testing the impact of pending changes to upstream dependencies.
You may wish to use these builds for your own testing ahead of our releases, you may include the SDK via the following Cargo.toml
entry:
c2pa = { git = "https://github.com/contentauth/c2pa-rs.git", branch = "nightly", features = [...]}
Commits in this branch have a modified sdk/Cargo.toml
entry which includes a version number similar to the following:
version = "0.25.3-nightly+2023-08-28-2f33ab3"
Please note that there is no formal support for code from a nightly release, but if you become aware of any issues, we would appreciate a bug report including this version number.
This section gives a highlight of noteworthy changes.
Refer to the CHANGELOG for detailed changes derived from git commit history.
14 July 2023
- (important!) the
add_thumbnails
feature is no longer tied tofile_io
, so you will need to specify it or thumbnails will not be generated. - removed
User
andUserCbor
assertions from public API. They were not generating correct manifest data. - use
manifest_add_labeled_assertion
instead - see docs onmanifest.embed
for an example. DataHash
andBoxHash
SDK support (generates a signed manifest ready to write into a file without writing to the file)- The SDK will no longer remove duplicate ingredients based on hash
make_test_images
updated to fix issue 195, actions without required ingredients- updated the test fixtures generated by make_test_images
- Expose
CAIRead
andCAIWrite
traits required by some SDK calls. - Bug fix for certain BMFF formats (AVIF) that causes images to be unreadable
21 June 2023
- Bump minor version to 0.24.0 to signify change in signature (back to the compatible one)
- Reverts to 1.2 Cose signatures when signing while still validating 1.3 Cose signatures
- We want to allow some time for clients to upgrade to validating 1.3 before writing this breaking change.
- Fix embed_from_memory to correctly return the updated image
- includes the cert serial number in the ValidationInfo output
- support adding claim_generator_info field
- support Actions V2 and Ingredients V2
- BMFF V2
- Json Schema generation
23 March 2023
- Added support for many new file formats, see Supported File Formats above.
- New api to return supported formats.
- Streaming APIs for manifest creation without file_io for some formats.
- Manifest and Ingredient JSON formats replace the
is_parent
field withrelationship
. - ResourceRef replaces
content-type
withformat
. - The
bmff
feature no longer required.