[
https://issues.apache.org/jira/browse/PDFBOX-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401258#comment-17401258
]
Michael Klink commented on PDFBOX-5261:
---------------------------------------
Both [^file.pdf] and unsigned.pdf (in [^unsigned.part1.rar]...) have hybrid
cross references. In [^file_signed.pdf], though, we see that the incremental
update created for the signature has a pure cross reference stream. That is
invalid:
* If a file has been started with a pure cross reference table or hybrid
references, all incremental updates must also use pure cross reference tables
or hybrid references.
* If a file has been started with a pure cross reference stream, all
incremental updates must also use pure cross reference streams.
> Signing a full scanned PDF causes "The signature byte range is invalid"
> -----------------------------------------------------------------------
>
> Key: PDFBOX-5261
> URL: https://issues.apache.org/jira/browse/PDFBOX-5261
> Project: PDFBox
> Issue Type: Bug
> Affects Versions: 3.0.0 PDFBox
> Reporter: Bryan
> Priority: Major
> Attachments: file.pdf, file_signed.pdf, unsigned.part1.rar,
> unsigned.part2.rar, unsigned.part3.rar
>
>
> Signing with:
> * pdfbox-app-3.0.0-20210804.050614-2786.jar causes the invalid signature.
> * pdfbox-app-2.0.24.jar causes a valid signature.
> By full scanned document I mean that the document is full of images.
> The attachment "unsigned.pdf" is the first file that I couldn't sign.
> The attachment "file.pdf" is the second file that I couldn't sign also.
> The attachment "file_signed.pdf" is the result of signing "file.pdf". With
> Adobe Reader you can check that the signature is invalid.
> Maybe it is related to having tables and images in the document.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
