Skip to content

Commit bd1d441

Browse files
authored
Merge pull request #272 from contentauth/trust-cleanup
Trust cleanup
2 parents f3a57f2 + c7e0449 commit bd1d441

File tree

8 files changed

+26
-447
lines changed

8 files changed

+26
-447
lines changed

docs/conformance.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The C2PA conformance program covers:
1212
- [Certificate authorities (CAs)](#certificate-authorities).
1313

1414
:::info
15-
If you're developing a product that reads or creates Content Credentials, you can apply for the C2PA conformance program. If accepted, the product is added to the [conforming products list](https://github.com/c2pa-org/conformance-public/blob/main/conforming-products/conforming-products-list.json#L302), which indicates it is compliant with the C2PA Content Credentials specification.
15+
If you're developing a product that reads or creates Content Credentials, you can apply for the C2PA conformance program. If accepted, the product is added to the [conforming products list](https://github.com/c2pa-org/conformance-public/blob/main/conforming-products/conforming-products-list.json), which indicates it is compliant with the C2PA Content Credentials specification.
1616

1717
**To start the process, fill out C2PA's [expression of interest form](https://docs.google.com/forms/d/e/1FAIpQLScERZH5rKfoeSu3y6gGbkllkyeAhmF0G-kXS0eXpb2vR238Rg/viewform).**
1818
:::

docs/getting-started/faqs.mdx

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,10 @@ hide_table_of_contents: true
66

77
import TOCInline from '@theme/TOCInline';
88

9+
:::tip See also
10+
[C2PA FAQs](https://c2pa.org/faqs/).
11+
:::
12+
913
<TOCInline toc={toc} />
1014

1115
### Are Content Credentials alone sufficient to prevent the spread of misinformation?
@@ -18,7 +22,7 @@ Content provenance is most effective when combining three key technologies:
1822

1923
Using these technologies together creates a more robust content provenance system than any single approach alone.
2024

21-
For more details, see [Durable Content Credentials](https://contentauthenticity.org/blog/durable-content-credentials) (April 8, 2024).
25+
For more details, see [Durable Content Credentials](../durable-cr/index.md).
2226

2327
### Are Content Credentials a blockchain system?
2428

@@ -31,9 +35,9 @@ Notable implementations using blockchain:
3135

3236
### Are Content Credentials about digital rights management?
3337

34-
No; Content Credentials do not enforce permissions for access to content. In many cases, the name displayed on the [Verify website](https://verify.contentauthenticity.org) is the name of the exporter of the content, not the rights owner.
38+
No; Content Credentials do not enforce permissions for access to content. In many cases, the name displayed by validator products such as the [**Inspect tool on Adobe Content Authenticity (Beta)**](https://verify.contentauthenticity.org) (ACA Inpsect) is the name of the exporter of the content, not the rights owner.
3539

36-
The [Title and signgin information](verify.mdx#title-and-signing-information) in Verify refers to the name of the exporter. If the image was created with an Adobe Product such as Photoshop with Content Credentials (Beta) enabled, the "Produced by" section shows the name of the Adobe ID associated with the user who exported the image.
40+
The [Title and signing information](aca-inspect.mdx#title-and-signing-information) in ACA Inspect refers to the name of the exporter. If the image was created with an Adobe Product such as Photoshop with Content Credentials (Beta) enabled, the "Produced by" section shows the name of the Adobe ID associated with the user who exported the image.
3741

3842
### Do Content Credentials indicate if an image is fake or altered?
3943

@@ -53,6 +57,8 @@ Conversely, if you use a C2PA-enabled camera to take a photo of an image, the ca
5357

5458
The C2PA specification allows for recovery of metadata stripped from an asset through a lookup process using either a watermarked ID or a perceptual content-aware hash, also referred to as a [fingerprint](https://c2pa.org/specifications/specifications/2.0/specs/C2PA_Specification.html#_fingerprint).
5559

60+
Durable Content Credentials helps content provenance to persist across content platforms by using C2PA manifest data. For more information, see [Durable Content Credentials](../durable-cr/index.md).
61+
5662
### What information is embedded in Content Credentials?
5763

5864
The information embedded in Content Credentials is totally up to each implementor.

docs/getting-started/index.mdx

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -87,11 +87,15 @@ In practice, to use a certificate with the CAI SDK, follow this process:
8787
For more information on getting and using certificates, see [Signing and certificates](signing/index.md).
8888
:::
8989

90-
### Interim trust list
90+
### Trust lists
9191

9292
import verify_unknown_source from '@site/static/img/verify-cc-unknown-source.png';
9393

94-
The C2PA [Verify tool](https://verify.contentauthenticity.org) uses a list of _known certificates_ (sometimes referred to as a "trust list") to determine whether a Content Credential was issued by a known source. Currently, it uses the [interim trust list](verify-known-cert-list) but it will be updated soon to use the official [C2PA trust list](conformance.mdx#c2pa-trust-lists).
94+
The _C2PA trust list_ is a curated list of certification authorities (CAs) that are authorized to issue signing certificates for conforming generator products.
95+
96+
Conforming validator products such as the [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) use the C2PA trust list to determine whether a Content Credential was issued using a certificate that can be traced back to a CA on the C2PA trust list.
97+
98+
Before the introduction of the C2PA trust list, during the early adoption phase of C2PA the C2PA [Verify tool](https://verify.contentauthenticity.org) used [the interim trust list](trust-list.mdx) to determine which certificates were considered valid and prevent unknown signers from appearing as valid. Verify will be updated to use the official [C2PA trust list](conformance.mdx#c2pa-trust-lists).
9599

96100
## Identity
97101

@@ -141,14 +145,15 @@ The example shown below illustrates one way to implement levels of disclosure:
141145

142146
## Example uses
143147

144-
Numerous Adobe tools and products implement Content Credentials. You can optionally attach credentials to images you create or modify using [Photoshop](https://helpx.adobe.com/photoshop/using/content-credentials.html) and [Lightroom](https://helpx.adobe.com/lightroom-cc/using/content-credentials-lightroom.html). Additionally, all images created using the [Firefly](https://blog.adobe.com/en/publish/2023/03/21/bringing-gen-ai-to-creative-cloud-adobe-firefly) generative AI tool automatically have attached Content Credentials. [Behance displays Content Credentials](https://www.behance.net/blog/cai-on-behance) if they are attached to media shared on the site, and still images provided through [Adobe Stock](https://stock.adobe.com/) automatically have Content Credentials attached.
148+
Numerous Adobe tools and products implement Content Credentials. For example, you can optionally attach credentials to images you create or modify using [Photoshop](https://helpx.adobe.com/photoshop/using/content-credentials.html) and [Lightroom](https://helpx.adobe.com/lightroom-cc/using/content-credentials-lightroom.html). Additionally, all images created using the [Firefly](https://blog.adobe.com/en/publish/2023/03/21/bringing-gen-ai-to-creative-cloud-adobe-firefly) generative AI tool automatically have attached Content Credentials. [Behance displays Content Credentials](https://www.behance.net/blog/cai-on-behance) if they are attached to media shared on the site, and still images provided through [Adobe Stock](https://stock.adobe.com/) automatically have Content Credentials attached. Other Adobe products also support Content Credentials.
145149

146-
The C2PA's [Verify website](https://verify.contentauthenticity.org/) inspects image files and displays their Content Credentials if they exist. See [Using the Verify tool](verify/) for more information.
150+
The [Inspect tool on Adobe Content Authenticity (Beta)](https://verify.contentauthenticity.org) inspects image files and displays their Content Credentials if they exist. See [Using ACA Inspect](aca-inspect.mdx) for more information.
147151

148152
Additionally, several other organizations have implemented CAI solutions, including:
149153

150-
- [**PixelStream**](https://contentauthenticity.org/eyes-on-provenance-pixelstream): A version-controlled sharing platform for authentic media. It's kind of like GitHub for authentic media assets, but it's built on top of C2PA tooling instead of Git.
154+
- [**PixelStream**](https://pixelstream.com/): Provides a complete end-to-end C2PA Content Credentials based authenticity platform that encapsulates the entire authenticity lifecycle of an asset from capture/creation, through editing, distribution via CDN, and finally to display.
155+
- [**ProofMode**](https://proofmode.org/): Provides an ecosystem of open-source tools and systems, including CAPTURE, a camera app with built-in provenance and authentication for chain-of-custody and VERIFY, a multi-purpose tool to inspect metadata and detect AI in images, audio, and video.
151156
- [**SmartFrame Technologies**](https://smartframe.io/blog/smartframe-and-cai-working-together-to-validate-provenance-and-improve-image-protection/): Validating provenance with secure capture to enhance innovative image streaming delivery.
152157
- [**The New York Times R&D**](https://rd.nytimes.com/projects/using-secure-sourcing-to-combat-misinformation): Using secure sourcing to combat misinformation in news publishing.
153158

154-
For more case studies, see [https://contentauthenticity.org/case-studies](https://contentauthenticity.org/case-studies).
159+
For more case studies, see [CAI Blog](https://contentauthenticity.org/blog).

0 commit comments

Comments
 (0)