[
https://issues.apache.org/jira/browse/PDFBOX-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Chojecki resolved PDFBOX-1857.
-------------------------------------
Resolution: Duplicate
Assignee: Thomas Chojecki
You got two problems here.
1.) Attaching content after signing.
2.) Problem with the id management.
1.) not solvable right now (see PDFBOX-1837). We would need to change the
object storing engine and rewrite the writer. So if you want to attach content,
you should do it before the first sign, or remove the signature before
attaching content and then you can sign again.
2.) I looked in the specification PDF3200-1:2008 at the chapter 14.4 and can
confirm the solution that was mentioned on stackoverflow.
nonetheless i close it as duplicated, because the main problem is the broken
signature.
> Attachment damages singature
> ----------------------------
>
> Key: PDFBOX-1857
> URL: https://issues.apache.org/jira/browse/PDFBOX-1857
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing, PDFReader, Signing, Utilities, Writing
> Affects Versions: 1.8.3, 1.8.4, 2.0.0
> Reporter: jack
> Assignee: Thomas Chojecki
> Priority: Blocker
> Attachments: attach.txt, original.pdf, original[signed].pdf,
> original[with-attachment].pdf, original[with-attachment][signed].pdf
>
>
> I have PDF document.
> 1) Adobe reader reads document well.
> 2) I sign document (using pdfbox-examples) and everything is well
> 3) Then I try to attach file to original PDF (Code is written in the pdfbox
> web page - in the cookBook).
> 4) Adobe reader reads attached document well. everything is well.
> 5) Now I have document with attachment.
> 6) I try to sign that document (I mean document with attachment). And I have
> 2 problem:
> First:
> when I open document, Adobe reader tells me that signature byte range is
> invalid.
> Second:
> when I try to close document (I mean to close adobe reader), Adobe reader
> tells me that:
> Do you want to save changes to "original[with-attachment][signed]" before
> closing?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
