<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - support for digital signatures" href="https://bugs.freedesktop.org/show_bug.cgi?id=16770#c64">Comment # 64</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - support for digital signatures" href="https://bugs.freedesktop.org/show_bug.cgi?id=16770">bug 16770</a> from <a class="email" href="mailto:ajohnson@redneon.com" title="Adrian Johnson <ajohnson@redneon.com>"> Adrian Johnson</a> <pre>(In reply to Andre Guerreiro from <a href="show_bug.cgi?id=16770#c63">comment #63</a>) > I also thought of adding the feature to pdfinfo but it seems wrong to mix up > something which performs various computations and relies on external state > (NSS cert DB) to pdfinfo which just reads metadata from the file itself. pdfinfo already performs various computations. If the file is encrypted it has to decrypt the objects to read the file. Reading from other sources is not an issue if a switch is used to enable the signature checking. It seems pointless to me to add an entire new utility to perform one function that can be enabled by adding a switch to pdfinfo. I'll leave it to Albert decide. But if we keep pdfsigverify I suggest making it more generic to allow for the possibility of later adding the capability to sign pdfs. eg call it pdfsig and if verifying signatures it not a fast operation, maybe enable the check with a switch and make the default operation (ie no switch specified) report whether the pdf contains a signature.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>