Skip to content

Commit 270367d

Browse files
committed
add link
1 parent daad7ae commit 270367d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/signing/get-cert.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ To sign manifest claims, you must have an X.509 v3 security certificate and key
1313
## Purchasing a certificate
1414

1515
:::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.
1717
:::
1818

1919
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

Comments
 (0)