[
https://issues.apache.org/jira/browse/PDFBOX-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880871#comment-13880871
]
Thomas Chojecki commented on PDFBOX-1780:
-----------------------------------------
Never ending story. If I revert locally the COSWriter change, some documents
can't be signed twice again and some can.
I can't find the root cause for this behaviour. I'm testing with the 1.8.3
release right now and got also the problem that at least one document can't be
parsed properly after creating a second signature. Adobe has no problem reading
the document and the signatures.
> 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)
