Signing with certificates

[Softbox44]

Is there any documentation on howto generate abd set certificates up. And what the difference is between the 3 certificate types.
thanks!

[sbplat]

You can generate keys and certificates (self-signed) using openssl. The different types are the formats we directly support, so for other types, you will need to convert them using something like keytool.

[Softbox44]

Thanks I will look into it. Openssl usually works with key pairs. How does that integrate with Sterling? I upload thr public key I guess. And what would the purpose be? Would the pdf file be encrypted?

…

On Fri, 22 Mar 2024, 01:36 Eric, ***@***.***> wrote: You can generate keys and certificates (self-signed) using openssl. The different types are the formats we directly support, so for other types, you will need to convert them using something like keytool. — Reply to this email directly, view it on GitHub <#941 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BG62B2R3H46TU53KFRYUG5DYZMD75AVCNFSM6AAAAABFBH446GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQNRYGQ4DC> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[sbplat]

1. Yes, you would upload the public key. You should be using a registered certificate issued by a certificate authority as a self-signed one cannot be validated.
2. The purpose is for recipients to be able to verify the legitimacy of the document.
3. No, this feature does not add a password to the PDF. Use add password for that.

[Softbox44]

So do I need to send my public key to the recipient as well so they can verify authenticity?

…

On Sat, 23 Mar 2024, 05:41 Eric, ***@***.***> wrote: 1. Yes, you would upload the public key. You should be using a registered certificate issued by a certificate authority as a self-signed one cannot be validated. 2. The purpose is for recipients to be able to verify the legitimacy of the document. 3. No, this feature does not add a password to the PDF. Use add password for that. — Reply to this email directly, view it on GitHub <#941 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BG62B2UBPCPJYM52X4Z4H23YZSJQ5AVCNFSM6AAAAABFBH446GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQOBSGUZDI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[sbplat]

If it's a self-signed one then they would need to trust your certificate.

[Frooodle]

But yes this is correct

Sign with private, verify with public

So can send public to other people to verify the pdf came from you

[Softbox44]

So the certificate is not used to encrypt any data and if its self signed it also doesn't provide trust. What is the functionality used for then? I am just trying to understand what i can achieve by setting it up.

…

On Sat, 23 Mar 2024, 11:09 Eric, ***@***.***> wrote: If it's a self-signed one then they would need to trust your certificate. — Reply to this email directly, view it on GitHub <#941 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BG62B2RZRUSRLQ7ZWL7LWQLYZTP6PAVCNFSM6AAAAABFBH446GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQOBTHE4TO> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[sbplat]

There's not much use for self-signed certs. They're mainly used internally such as for testing locally (shouldn't be used in production envs).

You can read more about certificate signatures here: https://helpx.adobe.com/ca/acrobat/kb/certificate-signatures.html