[
https://issues.apache.org/jira/browse/PDFBOX-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Chojecki updated PDFBOX-1822:
------------------------------------
Attachment:
SignatureFileSet-PDFBOX-1.8.2_TO_1.8.4-SNAPSHOT_SEQ_AND_NONSEQ.zip
I have attached a zip with a set of files. The files represent the signing
results between the pdfbox versions 1.8.2 and 1.8.4-SNAPSHOT and two examples
done with NonSeq parser.
The document I used for the signatures (ToBeSigned.pdf) is valid, already
signed and use a XRefStream.
*Result:*
NonSeq does not work at all. It copy the whole document instead of only writing
affected objects.
1.8.2 - has problem attaching a second signature on this kind of document.
*does not work*
1.8.3 - solves this problem. *work*
1.8.4-SNAPSHOT - is the latest 1.8.x branch without the patch from this Issue.
*work*
1.8.4-SNAPSHOT_WITH_PDFBOX-1822_PATCH - is the version with the patch from this
issue. *does not work* Instead of an XRefStream a XRefTable was wrote. Make no
sense in this case.
The biggest problem is, all JUnit tests went well. I checked each document with
the latest Adobe Reader to find the problems.
> Signature byte range is Invalid
> -------------------------------
>
> Key: PDFBOX-1822
> URL: https://issues.apache.org/jira/browse/PDFBOX-1822
> Project: PDFBox
> Issue Type: Bug
> Components: Parsing, PDModel, PDModel.AcroForm, Signing
> Affects Versions: 1.8.3, 1.8.4, 2.0.0
> Reporter: vakhtang koroghlishvili
> Assignee: Andreas Lehmkühler
> Fix For: 1.8.4, 2.0.0
>
> Attachments:
> SignatureFileSet-PDFBOX-1.8.2_TO_1.8.4-SNAPSHOT_SEQ_AND_NONSEQ.zip,
> araxis-merge - compare two document.jpg, damaged-sig.jpg,
> unsigned-signed.pdf, unsigned.pdf, unsigned_signed_fix.pdf
>
>
> On person send me a unsigned PDF document. He wanted to sign it. When I try
> to sign it (using pad box), I have some problem.
> After signing adobe reader tells me "The signature byre range is invalid".
> I will attach original and signed document.
> I think, it is PDF box parser error. another signature libraries sign
> document very well. I'm searching the problem at the moment, in order to fix
> it.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
