(In reply to Markus Wernig from comment #104)
> I think the correct statement to issue in this case would be that a part
> ("revision") of the PDF has been signed and to show the validation result
> for that revision, ideally giving the user a chance to view only the signed
> part.
>
> This might even be indispensable when there are multiple signatures applied
> to the document.
So one idea could be to also use the first offset when checking the
signature and in case it is not zero instead of return the status as
SIGNATURE_VALID say something like "SIGNATURE_PARTLY_VALID".
The pdfsig tool already implements support for multiple
signatures/"revisions" but it seems the API does not expose the
ByteRange for which the signature covers nor provides an other way to
obtain that revision of the document (?).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
Title:
verify digital signatures
Status in Evince:
Confirmed
Status in Poppler:
Confirmed
Status in poppler package in Ubuntu:
Triaged
Bug description:
Binary package hint: evince
This is a feature request to verify digital signatures. I'm receiving more
and more digitally signed PDF's and evince already acknowledges them with:
Signature Not Verified
Digitally signed by <signer>
Date: <time stamp>
Reason: <reason>
Location: <location>
but it would be great if Evince would be integrated into the distro's
ca-certificate infrastructure to verify these signatures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
