[
https://issues.apache.org/jira/browse/PDFBOX-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926816#comment-17926816
]
Tilman Hausherr commented on PDFBOX-5954:
-----------------------------------------
No the file is ok (a length of 0 is fine), but yes the changes to the
validateStreamLength method are the cause. We need to change that one that it
doesn't complain about a 0 length if it is valid, or if not possible, that it
complains quietly, e.g. only in debug mode.
> Invalid stream length: 0, stream start position: <xxx>
> ------------------------------------------------------
>
> Key: PDFBOX-5954
> URL: https://issues.apache.org/jira/browse/PDFBOX-5954
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing
> Affects Versions: 2.0.33, 3.0.4 PDFBox
> Reporter: Joost Konst
> Priority: Minor
> Attachments: pdfa-signed.pdf
>
>
> Ever since updating to version 2.0.33 we have been getting the following
> warning when handling PDF's with digital signatures:
> {code:java}
> Invalid stream length: 0, stream start position: xxx{code}
> It gets logged up to 10 times every time a PDF with a signature gets sent.
> This issue could be related to PDFBOX-5880 that's in the 2.0.33 release,
> because I reverted to the 2.0.32 version and the warnings disappear.
> I've attached the PDF file that seems to cause these warnings
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
