Closed ousia closed 5 years ago
Interesting. New undocumented feature... But thank you for the test files!
The -3 version in copr is built with openssl now. That gets rid of the "no openssl support" error but core dumps anyways (besdies error about Sig widgets). (If I use the wrong password I get an error about that, then the core dump; with the correct password only the core dump).
It would be interesting to know if this works somewhere else.
It didn’t work in Windows, with the binaries provided by Artifex.
I opened a bug report with the proper backtrace and let’s see what happens.
I’m not closing the issue before the people from Artifex answer my request.
Well, Artifex released the stable version with no visible fix for the issue.
Well, I don’t know whether they might do anything to prevent the segmentation fault.
But for now, all I can say is that I don’t have any idea of what Artifex considers with the new feature:
- [c]an verify and sign digital signatures.
I must confess it is beyond my knowledge. But since this is an upstream issue, I’m closing this one.
The issue seems to be fixed in current master .
Just in case you would be interested in packaging the current master.
Do you know which commit in master fixed that?
I'm hunting down a few of the fixes for current CVEs before I submit 1.14.0.
@mjg,
I tried to sign a PDF document containing a signature field and I got a segmentation fault with an error about lacking OpenSSL support (sample certificate with password
123456
.)Could you enable OpenSSL or do I have to report a bug upstream?
Many thanks for your help.