Skip to content

Commit 0af1bfd

Browse files
committed
Add prereqs, fix list formatting
1 parent 1e60315 commit 0af1bfd

File tree

1 file changed

+37
-21
lines changed

1 file changed

+37
-21
lines changed

docs/trust-list.mdx

Lines changed: 37 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -28,42 +28,58 @@ The [contentcredentials.org](https://contentcredentials.org/) site hosts the fol
2828

2929
## Checking your certificate
3030

31-
Before requesting to add your signing certificate to the known certificate list, perform a preliminary check on your certificate by following these steps:
31+
Before requesting to [add your signing certificate to the known certificate list](#how-to-add-a-certificate-to-the-list), perform a preliminary check to ensure the certificate is configured properly.
32+
33+
### Prerequisites
34+
35+
The preliminary certificate check procedure below requires the following tools. You must install them if you haven't done so already:
36+
37+
- [jq](https://jqlang.org/), a lightweight and flexible command-line JSON processor. On macOS, if you have [Homebrew](https://brew.sh/), you can install jq by entering `brew install jq`.
38+
- [OpenSSL](https://www.openssl.org/), a cryptographic software library and CLI. It's installed on many systems such as macOS (but make sure you have a recent version). If OpenSSL is not installed on your system, see the [list of unofficial binary distributions](https://wiki.openssl.org/index.php/Binaries).
39+
- [C2PA Tool](c2patool/readme.md), the command line tool for working with C2PA manifests and media assets.
40+
41+
### Procedure
42+
43+
:::note
44+
In the example commands given below, `cert.pem` is your certificate file.
45+
:::
46+
47+
Check your certificate by following these steps:
3248

3349
1. **Ensure that signing with the certificate doesn't have any validation errors** by using a C2PA Tool command like this:
3450

35-
```
36-
c2patool ./image.jpg trust --allowed_list ./cert.pem
37-
```
51+
```
52+
c2patool ./image.jpg trust --allowed_list ./cert.pem
53+
```
3854

39-
Confirm that the result does not contain a `validation_status` field, which indicates an error.
55+
Confirm that the result does not contain a `validation_status` field, which indicates an error.
4056

4157
1. **Confirm that the `signature_info.issuer` field in the manifest is correct**. This field determines what [Verify displays for the organization name](verify.mdx#title-and-signing-information) after "Issued by ...". Use a C2PA Tool command like this:
4258

43-
```
44-
c2patool ./image.jpg trust --allowed_list ./cert.pem \
45-
| jq --args '.manifests[].signature_info.issuer'
46-
```
59+
```
60+
c2patool ./image.jpg trust --allowed_list ./cert.pem \
61+
| jq --args '.manifests[].signature_info.issuer'
62+
```
4763

48-
The response should be something like this:
64+
The response should be something like this:
4965

50-
```
51-
"XYZ Inc."
52-
```
66+
```
67+
"XYZ Inc."
68+
```
5369

54-
Where "XYZ Inc." is the name of your organization.
70+
Where "XYZ Inc." is the name of your organization.
5571

5672
1. **Use `openssl` to perform basic verification of the certificate** you're submitting; for example:
5773

58-
```
59-
openssl x509 -noout -text -in 'cert.pem' | grep 'Subject:'
60-
```
74+
```
75+
openssl x509 -noout -text -in 'cert.pem' | grep 'Subject:'
76+
```
6177

62-
Example response:
78+
Example response:
6379

64-
```
65-
Subject: organizationIdentifier=XYZ-7155227, C=US, ST=Delaware, L=Dover, O=Whatever Inc., SN=xxx, GN=xxx, CN=xxx
66-
```
80+
```
81+
Subject: organizationIdentifier=XYZ-7155227, C=US, ST=Delaware, L=Dover, O=Whatever Inc., SN=xxx, GN=xxx, CN=xxx
82+
```
6783

6884
## Using the known certificate list
6985

0 commit comments

Comments
 (0)