Hi friends.
I have a pair of Pdf signature modules, written in Java and Vb.net, using Bouncycastle, AbcPdf, and iText 2.1.7 libraries.
That modules add a timestamp token to the digital signature, provided by TSA RFC 3161 Servers.
We use different providers, for example:
http://ca.signfiles.com/TSAServer.aspx
Up to now, it works OK, but now, another TSA Server, seems to return a timestamp 'in a way' that Adobe Reader can't process.
That provider, says that they only send the message as RFC 3161 says... and the don't want to tell me more .... it's a pity.
Using that TimeStampToken, the signature it's showed in Reader, with "the signature has a timestamp -- unavailable timestamp", and in some versions, we can see the "show certificate button".... but Adobe Reader crashes in "PPKLite.api!281b7a3c()" method (debugging with Visual studio 2010).
Now, my question: how? or, which tool? could help me to discover what it's wrong in the timestamp token we are adding to our PDFs?
Any idea will be wellcome