64 results found
-
Bug: ECDSA signature encoded incorrectly
I have encountered a bug in Acrobat Reader DC that is related to encoding of ECDSA digital signatures. The signature is composed of two numbers. It seems that when the highest bit of those numbers is set it is not padded with zero to make sure that the number is treated as positive integer. Instead it is treated as a negative integer. Adobe itself treats those signatures as valid, but other software refuses to accept them. Our nationwide eID uses ECC, so this bug impacts a large number of users. I can provide test file with valid and invalid signatures…
1 vote -
Allow the option to add today's date with Fill & Sign.
I frequently have to sign timesheets that have been scanned on to email. (i.e Flat form without autofull fields) Adding my signature is easy, but I have to type the date out as text. Having an extra button that allows the date to be added, without having to type it would be fantastic.
2 votes -
stop Fill & Sgn notification
Stop the notification of "Who needs to Fill & Sign"? i beg of you. i do 30-50 invoices a day. by the end i want to pull my hair out with this.
having notification a couple times but on every single time!!!
2 votes -
OCSP uses HTTPS even when OCSP URL specifies HTTP
Recently we have noticed certificate revocation checking failures with the latest version of Acrobat Reader DC.
In the Department of Defense, the OCSP URLs in the DOD PKI are "http://ocsp.disa.mil". These servers work. But they do not respond on the SSL-enabled port (https). But when we try to verify signatures with Acrobat DC, we get connection failures. Network tracing has revealed that even though the URLs in the certificate specify http, Adobe Reader is trying to connect to the https port, and this gets timeouts.
Environment: MacOS X
Steps to reproduce: Get a certificate that has an OCSP URL…2 votes
- Don't see your idea?