You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/signing/get-cert.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ To sign manifest claims, you must have an X.509 v3 security certificate and key
13
13
## Purchasing a certificate
14
14
15
15
:::note
16
-
The [C2PA conformance program](https://c2pa.org/conformance/) establishes the requirements governing the issuance of C2PA claim signing certificates for use by product developers. Through the end of 2025 you can still purchase a certificate from any CA and request to add it to the interim trust list, but starting in 2026 conforming generator products must use a certificate from a CA on the C2PA trust list. See [C2PA conformance program](conformance.mdx) for more information.
16
+
The [C2PA conformance program](https://c2pa.org/conformance/) establishes the requirements governing the issuance of C2PA claim signing certificates for use by product developers. Through the end of 2025 you can still purchase a certificate from any CA and request to add it to the [interim trust list](trust-list.mdx), but starting in 2026 conforming generator products must use a certificate from a CA on the C2PA trust list. See [C2PA conformance program](conformance.mdx) for more information.
17
17
:::
18
18
19
19
The process to purchase a certificate and key is different for each CA: You might be able to simply click a "Buy" button on the CA's website. Or your can make your own key and use it to create a certificate signing request (CSR) that you send to the CA. Regardless of the process, what you get back is a signed certificate that you use to create a certificate chain.
0 commit comments