On 17.03.2013 18:48, kap...@mizera.cz wrote:
be verified - the same as you had ... OpenSSL and Adobe conform to RFC 3161; but not this TSA ...correct, the error message means, that the received timestamp could notBut the discussed TSA postsignum would not exist at all if there would be a problem with signed PDF's (it is most used usage).
the other use is Microsoft Authenticode, but this is different protocol;
The problem there is that only OpenSSL fails to verify their TS's (what does not care them much, unfortunately).Adobe also fails ..., as I have tried ...; it would be nonsense, when the Test TSA fails and the Production TSA passes, because, they want money for generated time stamps, and nobody will trust this, because of failing Test TSA;
?=> it could be probably problem on yours side.
not really ...
What Adobe product and version are you using ? Maybe too old ?
not newest, but RFC 3161 is old, too
It is possible that Adobe has add attr.cert. support (CMS, ...).
can you please tell me, what an attr.cert is? because every cert has attributes ...
And does it work with another official TSA ? E.g. with TSA service: http://timestamp.comodoca.com/rfc3161
yes with this and some other; - timestamp.geotrust.com - universign.eu - ca.signfiles.com - tsa.starfieldtech.com
smime.p7s
Description: S/MIME Cryptographic Signature
