<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - make it possible to extract digital signature data (also in pdfsig)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99271#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - make it possible to extract digital signature data (also in pdfsig)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99271">bug 99271</a> from <a class="email" href="mailto:huj@froreich-bioscientia.de" title="Hans-Ulrich Jüttner <huj@froreich-bioscientia.de>"> Hans-Ulrich Jüttner</a> <pre>(In reply to oliver.sander from <a href="show_bug.cgi?id=99271#c38">comment #38</a>) > I tried to reproduce the crash with the file from <a href="show_bug.cgi?id=99271#c34">comment 34</a>, but I > couldn't. pdfsig appears to do what it is supposed to do. > > However, valgrind complains about a few things. Not sure whether that means > bugs in poppler, or bugs in libnss, though. I'll attach the log. As this is in the destructor, which as well as the constructor hasn't been touched by the patch, I would say this is a problem valgrind has with libnss3. However, in my version on a 32-bit system the problem doesn't show up. Maybe you could check pdfsig from the unpatched master branch with valgrind and a signed file which pdfsig from the master branch can handle (e.g. <a href="https://kbdeveloper.qoppa.com/wp-content/uploads/blank_signed.pdf">https://kbdeveloper.qoppa.com/wp-content/uploads/blank_signed.pdf</a>).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>