[
https://issues.apache.org/jira/browse/PDFBOX-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947924#comment-13947924
]
Maruan Sahyoun commented on PDFBOX-2001:
----------------------------------------
PDFBox has an issue parsing the document. Try loading with
PDDocument.loadNonSeq and you get a number of errors for wrong offset
information.
PDFBox doesn’t rely on the Sig key being present for the Type information of
the dictionary. So currently the parsing seems to be the root cause.
As you asked what our position about "But PDFBox seems to limit its research of
signature only if this key "Sig" is present. „ is - well this limitation
doesn’t seem to exist.
We will need to look into why the parsing fails.
> Digital Signature information
> -----------------------------
>
> Key: PDFBOX-2001
> URL: https://issues.apache.org/jira/browse/PDFBOX-2001
> Project: PDFBox
> Issue Type: Bug
> Affects Versions: 1.8.3
> Reporter: Nicolas Kaczmarski
> Attachments: D.1_signiert.pdf, acrobatSignatureExample.PNG
>
>
> We have a signed PDF but signature is described without key "Sig".
> As you can see in the standard PDF 32000-1:2008 - Table 252 - Entries in a
> signature dictionary, this key is optional :
> "(Optional) The type of PDF object that this dictionary describes; if
> present, shall be Sig for a signature dictionary. "
> But PDFBox seems to limit its research of signature only if this key "Sig" is
> present.
> What is your position about that?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
