[
https://issues.apache.org/jira/browse/PDFBOX-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879939#comment-13879939
]
Andreas Lehmkühler commented on PDFBOX-1780:
--------------------------------------------
I had a quick look and it seems that the second part isn't needed. There is no
need to divide into direct and indirect objects the "subValue.accept( this )"
shall handle this.
Sorry that I didn't saw that in the first place when aplying the patch. We
should revert that part. I'm going to do that later, but within PDFBOX-1862 as
I don't want to reopen this one.
> 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)
