On Saturday, July 25, 2020 5:27:27 AM EDT Miguel A. Vallejo wrote: > I deleted the .mozilla directory, ran firefox to create it again and > now okular and pdfsig work just fine with the signed PDF. > > I don't understand anything. Does Okular depend on firefox? I think the bug you're hitting is #924050 in Poppler. Poppler uses NSS, and along with probably Firefox's certificate store, for figuring out which certificate authorities to trust. LibreOffice does a similar thing. If you try to sign a PDF with it, it will look to use client certificates in Firefox profiles.
> Thank you for your advice. I reverted the packages to the ones > available in sid. Now waiting for okular to upgrade.... I really miss > it when working with these PDF files Yes, Okular's documentation says Poppler 0.73 is needed for full PDF signature functionality whereas Buster and Sid have 0.71. In particular, I believe a newer Poppler would close Okular #819728 by enabling checking the certificate authorities as well. I recently got in touch with the most recent Poppler uploader Emilio asking about its status. The wait hopefully won't be too long; his working plan was to get 0.90 (released a couple weeks ago) into experimental sometime, and then transition that later. There's just a few blocking packages that need handholding to work, Okular not being one of those.
signature.asc
Description: This is a digitally signed message part.
