[
https://issues.apache.org/jira/browse/PDFBOX-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879934#comment-13879934
]
Thomas Chojecki commented on PDFBOX-1780:
-----------------------------------------
The patch contains two parts.
One is the "setDirect" which fix the PDFBOX-1314 issue. So the parser know
which document was written directly and save this behaviour.
This part fix also the signature problematic for at least my problematic
documents with multiple signatures over different pages.
The second is the COSWriter patch. What does this patch do? This line broke the
signature creation for at least one document see PDFBOX-1862. Do we need this?
Can we maybe revert it?
> previous revision is damaged after signing
> ------------------------------------------
>
> Key: PDFBOX-1780
> URL: https://issues.apache.org/jira/browse/PDFBOX-1780
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing, Signing, Writing
> Affects Versions: 1.8.2
> Reporter: vakhtang koroghlishvili
> Assignee: Andreas Lehmkühler
> Priority: Critical
> Fix For: 1.8.3, 2.0.0
>
> Attachments: fixed.jpg, fixed.patch, original-signed -[FIXED].pdf,
> original-signed [DAMAGED].pdf, original-signed [ORIGINAL].pdf
>
>
> Ihave PDF file which was signed by some other application. When I try to
> sign it with PDFbox, previous revision is damaged. I have discussion at
> stackoverflow, with Michael Klink.
> http://stackoverflow.com/questions/19903884/pdf-document-is-modified-by-another-revision/19905271?noredirect=1#19905271
> when we see some changes merely was structural. Some changes was just
> rounding problem - PDFBOX-1778.
> When I test, problem of damaged signature was caused from structural change
> [when there must be direct reference, there was indirect reference and etc..]
> So we solve that problem. I will upload damaged PDF document, fixed pdf, and
> the patch too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
