You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/09/28 06:55:00 UTC

[jira] [Commented] (PDFBOX-5521) Signing tries to set byteRange of old signature

    [ https://issues.apache.org/jira/browse/PDFBOX-5521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610376#comment-17610376 ] 

ASF subversion and git services commented on PDFBOX-5521:
---------------------------------------------------------

Commit 1904317 from Tilman Hausherr in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1904317 ]

PDFBOX-5521: detect and avoid old signatures in the incrementally saved part

> Signing tries to set byteRange of old signature
> -----------------------------------------------
>
>                 Key: PDFBOX-5521
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-5521
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Signing
>    Affects Versions: 2.0.27
>            Reporter: Tilman Hausherr
>            Assignee: Tilman Hausherr
>            Priority: Major
>             Fix For: 2.0.28, 3.0.0 PDFBox
>
>
> A long bug report on the users mailing lists leads to the finding that the COSWriter code hits an "old" signature that is (for whatever reason, maybe it was incorrectly included) present in the incremental part. The signing then fails because the byte range to be written is longer than the existing byte range.
> To avoid this, we improve signature detection by checking that the size indicated by byteRange is higher than the existing PDF size.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org