I've pushed your patch with some fixlets from my side to
http://cgit.freedesktop.org/poppler/poppler/log/?h=signatureHandling

I have three questions we need to answer before i merge it to master:
 * Do we really want to make NSS mandatory?
 * Do we want to provide a way for frontends to give their own path to a nss 
database?
 * Do we want to first support other signatures like adbe.x509.rsa_sha1 ?

Also i've no clue if the implementation is correct, it seems to do nice
things with some files i have laying around.

Comments?

-- 
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

Reply via email to