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
The `c2patool` uses some custom properties in the `cawg_x509_signer` section of the settings file for signing:
4
+
5
+
-`private_key`: Path to the private key file.
6
+
-`sign_cert`: Path to the signing certificate file.
7
+
-`alg`: Algorithm to use, if not the default ES256.
8
+
9
+
Both the private key and signing certificate must be in PEM (privacy-enhanced mail) format. The signing certificate must contain a PEM certificate chain starting with the end-entity certificate used to sign the claim ending with the intermediate certificate before the root CA certificate.
10
+
11
+
If the settings file doesn't include the `cawg_x509_signer.sign_cert` and `cawg_x509_signer.private_key` properties, c2patool will not generate a CAWG identity assertion. An example settings file demonstrating how this works is provided in the [c2patool repo sample folder](https://github.com/contentauth/c2pa-rs/tree/main/cli/tests/fixtures/trust/cawg_sign_settings.toml).
12
+
13
+
If you are using a signing algorithm other than the default `es256`, specify it in the manifest definition field `alg` with one of the following values:
14
+
15
+
-`ps256`
16
+
-`ps384`
17
+
-`ps512`
18
+
-`es256`
19
+
-`es384`
20
+
-`es512`
21
+
-`ed25519`
22
+
23
+
The specified algorithm must be compatible with the values of private key and signing certificate. For more information, see [Signing manfiests](https://opensource.contentauthenticity.org/docs/signing-manifests).
24
+
25
+
To sign an asset using this technique, adapt the following command-line invocation:
0 commit comments