timestamping signature size larger than expected in Adobe Acrobar reader

[Youcef5CF3]

Hello,

Using Acrobat Reader, I have been trying to apply timestamps on documents from a public timestamping server that I have configured. (a TSA that my company manages) Whenever I try to apply a timestamp the following error is returned: SigValue is 1903 bytes larger than expected.

After some investigation it turned out that when the timestamp token exceeds 7 Kb this error is returned, otherwise it would work fine, After further analysis we concluded that the size exceeds 7Kb due to the timestamp token including the whole TSA certificate chain which comprises of 4 CAs that all have 4096 key length.

Is there any further configurations that can be done on Adobe to allow sigvalue larger than what is expected?

[Serene_nature15C3]

Hi Youcef,

Hope you are doing well and sorry for the trouble. As per the issue description mentioned above, you are getting above-mentioned error when trying to creating a certificate signature on a PDF.

Could you let us know the version of Adobe Acrobat/ Reader DC and the operating system installed on the machine? To check the version of the application go to Help > About Acrobat and make sure you have the latest version installed. Go to Help > Check for Update reboot the computer once

Also please check out the similar discussion i have found - https://community.adobe.com/t5/acrobat/sigvalue-larger-than-expected/m-p/10042291 and see if that helps.

Regards

Amal

[Youcef5CF3]

Hello, this is the version I'm using

[Youcef5CF3]

Also using the latest Windows 10 enterprise 2016 with latest updates

[Serene_nature15C3]

Hi there

please check out the similar discussion - https://community.adobe.com/t5/acrobat/sigvalue-larger-than-expected/m-p/10042291 and see if that helps.

Regards

Amal

[Mustapha Abd25805490sdbj]

Hello Adobe Support,

Any update concerning this matter ?

we facing same issue as described by @Youcef5CF3 , we are unable to apply timestamp signature.

any possible solution ?

[janes_p]

Same issue here - any updates and/or solutions, Adobe?